[Touch-packages] [Bug 1879326] Re: DNS resolution ceased to work after update
Please find dpkg.log attached. I extracted with the following command timely suspects but of those 140 only 131 are unique. I do not know why unless there were updates twice for some reason. grep -F '2020-05-16 23:' /var/log/dpkg.log | grep -F 'status installed' 2020-05-16 23:12:46 status installed python3-more-itertools:all 4.2.0-1build1 2020-05-16 23:12:46 status installed python3-attr:all 19.3.0-2 2020-05-16 23:12:47 status installed qgis-providers-common:all 3.10.4+dfsg-1ubuntu2 2020-05-16 23:12:47 status installed python3-pyqt5.qtsql:amd64 5.14.1+dfsg-3build1 2020-05-16 23:12:47 status installed ttf-bitstream-vera:all 1.10-8 2020-05-16 23:12:48 status installed libfcgi0ldbl:amd64 2.4.0-10build1 2020-05-16 23:12:48 status installed libgslcblas0:amd64 2.5+dfsg-6build1 2020-05-16 23:12:48 status installed python3-ipython-genutils:all 0.2.0-1ubuntu1 2020-05-16 23:12:49 status installed libsqlite3-mod-spatialite:amd64 4.3.0a-6build1 2020-05-16 23:12:49 status installed fonts-lyx:all 2.3.4.2-2 2020-05-16 23:12:49 status installed libqscintilla2-qt5-l10n:all 2.11.2+dfsg-6 2020-05-16 23:12:49 status installed python3-retrying:all 1.3.3-4 2020-05-16 23:12:50 status installed libhdf5-cpp-103:amd64 1.10.4+repack-11ubuntu1 2020-05-16 23:12:50 status installed libfcgi-bin:amd64 2.4.0-10build1 2020-05-16 23:12:50 status installed qhelpgenerator-qt5:amd64 5.12.8-0ubuntu1 2020-05-16 23:12:51 status installed libqwt-qt5-6:amd64 6.1.4-1.1build1 2020-05-16 23:12:52 status installed libqt5serialport5:amd64 5.12.8-0ubuntu1 2020-05-16 23:12:53 status installed libspatialindex6:amd64 1.9.3-1build1 2020-05-16 23:12:54 status installed libqscintilla2-qt5-15:amd64 2.11.2+dfsg-6 2020-05-16 23:12:54 status installed libqt5designercomponents5:amd64 5.12.8-0ubuntu1 2020-05-16 23:12:55 status installed python3-zipp:all 1.0.0-1 2020-05-16 23:12:55 status installed libqt53dcore5:amd64 5.12.8+dfsg-0ubuntu1 2020-05-16 23:12:55 status installed libqt53dlogic5:amd64 5.12.8+dfsg-0ubuntu1 2020-05-16 23:12:56 status installed python3-webencodings:all 0.5.1-1ubuntu1 2020-05-16 23:12:56 status installed libqgis-native3.10.4:amd64 3.10.4+dfsg-1ubuntu2 2020-05-16 23:12:56 status installed libllvm10:amd64 1:10.0.0-4ubuntu1 2020-05-16 23:12:56 status installed libqgis-core3.10.4:amd64 3.10.4+dfsg-1ubuntu2 2020-05-16 23:12:57 status installed python3-decorator:all 4.4.2-0ubuntu1 2020-05-16 23:12:57 status installed libjs-jquery-ui:all 1.12.1+dfsg-5 2020-05-16 23:12:58 status installed python3-pyparsing:all 2.4.6-1 2020-05-16 23:12:58 status installed libgsl23:amd64 2.5+dfsg-6build1 2020-05-16 23:12:58 status installed libclang1-10:amd64 1:10.0.0-4ubuntu1 2020-05-16 23:12:58 status installed libassimp5:amd64 5.0.1~ds0-1build1 2020-05-16 23:12:59 status installed python3-cycler:all 0.10.0-3 2020-05-16 23:13:00 status installed qtattributionsscanner-qt5:amd64 5.12.8-0ubuntu1 2020-05-16 23:13:00 status installed python3-kiwisolver:amd64 1.0.1-3build1 2020-05-16 23:13:00 status installed grass-doc:all 7.8.2-1build3 2020-05-16 23:13:00 status installed libqt53dinput5:amd64 5.12.8+dfsg-0ubuntu1 2020-05-16 23:13:01 status installed libtcl8.6:amd64 8.6.10+dfsg-1 2020-05-16 23:13:01 status installed libqgis-gui3.10.4:amd64 3.10.4+dfsg-1ubuntu2 2020-05-16 23:13:01 status installed libqgis-analysis3.10.4:amd64 3.10.4+dfsg-1ubuntu2 2020-05-16 23:13:01 status installed python3-html5lib:all 1.0.1-2 2020-05-16 23:13:03 status installed python3-numpy:amd64 1:1.17.4-5ubuntu3 2020-05-16 23:13:03 status installed qt5-assistant:amd64 5.12.8-0ubuntu1 2020-05-16 23:13:03 status installed python3-pyrsistent:amd64 0.15.5-1build1 2020-05-16 23:13:04 status installed python3-pyqt5.qtwebkit:amd64 5.14.1+dfsg-3build1 2020-05-16 23:13:04 status installed liblaszip8:amd64 3.4.3-1build1 2020-05-16 23:13:04 status installed python3-lxml:amd64 4.5.0-1 2020-05-16 23:13:05 status installed libqgispython3.10.4:amd64 3.10.4+dfsg-1ubuntu2 2020-05-16 23:13:06 status installed libjs-leaflet:all 1.6.0~dfsg-1 2020-05-16 23:13:06 status installed python3-traitlets:all 4.3.3-3 2020-05-16 23:13:07 status installed libpdal-util9:amd64 2.0.1+ds-1build3 2020-05-16 23:13:07 status installed qgis-plugin-grass-common:all 3.10.4+dfsg-1ubuntu2 2020-05-16 23:13:08 status installed python-matplotlib-data:all 3.1.2-1ubuntu4 2020-05-16 23:13:08 status installed python3-lib2to3:all 3.8.2-1ubuntu1 2020-05-16 23:13:08 status installed python3-soupsieve:all 1.9.5+dfsg-1 2020-05-16 23:13:09 status installed python3-gdal:amd64 3.0.4+dfsg-1build3 2020-05-16 23:13:09 status installed python3-pyqt5.qsci:amd64 2.11.2+dfsg-6 2020-05-16 23:13:09 status installed python3-pyqt5.qtsvg:amd64 5.14.1+dfsg-3build1 2020-05-16 23:13:09 status installed python3-distutils:all 3.8.2-1ubuntu1 2020-05-16 23:13:51 status installed qgis-providers:amd64 3.10.4+dfsg-1ubuntu2 2020-05-16 23:13:52 status installed python3-matplotlib:amd64 3.1.2-1ubuntu4 2020-05-16 23:13:53 status installed
[Touch-packages] [Bug 1876065] Re: After unplug headphones and plug them again no sound can be heard
@Daniel van Vugt (vanvugt) A personal computer, laptop or desktop, at home is the most wanted thing in the lockdown in this corona season to work from home. A puter without audio is next to good for nothing. Since updating mine to 20.04 LTS on April 24, I have been running wall to post. Facing a lot of hardship to keep things straight without the audio working. If you could tell us the probable date of official update or pre- released update, it will be a ray of hope, a light at the end of the tunnel. -- 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/1876065 Title: After unplug headphones and plug them again no sound can be heard Status in pulseaudio package in Ubuntu: Fix Committed Status in pulseaudio source package in Focal: In Progress Status in pulseaudio source package in Groovy: Fix Committed Bug description: * Impact Sound isn't automatically redirected to headphones when those are connected to a jack interface * Test case Disconnect the headsets Start your webbrowser/music player/video player and play some sound Connect the headsets to the jack interface -> the sound should be directly redirected to the plugged headsets * Regression potential Check that audio routing when connecting/disconnecting devices to the hack entry is working correctly After startup with headset plugged in they play sound nicely - no issue. When they are unplugged, the sound is switched to the speaker (laptop) - all good. However, when I plug the headset back there is no sound. I see the app on pavucontrol, the volume is fine - everything looks fine except there is no sound. I dumped output of "pactl list" command on startup (headset plugged), after unplugging the headset, and when it is plugged back. From the comparison of these outputs, it looks like the source has got muted after the headset is plugged. Source #1 State: RUNNING Name: alsa_input.pci-_00_1f.3.analog-stereo Description: Built-in Audio Analog Stereo Driver: module-alsa-card.c Sample Specification: s16le 2ch 44100Hz Channel Map: front-left,front-right Owner Module: 7 Mute: yes Attached three outputs: headset-in.txt - after startup with headset plugged - all fine. headset-out.txt - after unplugged headset - sound through the speaker - all fine. headset-back.txt - after plugged headset back - no sound. Any help greatly appreciated. Regards, Roman To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1876065/+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 1879182] Re: Sound cuts off and back on randomly during online streaming of videos
It looks like the main problem here is that your kernel audio devices keep reappearing (and disappearing??): May 18 21:04:31 sidpc kernel: snd_hda_intel :00:1f.3: Applying patch firmware 'hda-jack-retask.fw' May 18 21:04:31 sidpc kernel: snd_hda_intel :00:1f.3: bound :00:02.0 (ops i915_audio_component_bind_ops [i915]) May 18 21:04:31 sidpc kernel: snd_hda_codec_realtek hdaudioC0D0: ALC1150: SKU not ready 0x May 18 21:04:31 sidpc kernel: snd_hda_codec_realtek hdaudioC0D0: autoconfig for ALC1150: line_outs=3 (0x14/0x15/0x16/0x0/0x0) type:line May 18 21:04:31 sidpc kernel: snd_hda_codec_realtek hdaudioC0D0: speaker_outs=0 (0x0/0x0/0x0/0x0/0x0) May 18 21:04:31 sidpc kernel: snd_hda_codec_realtek hdaudioC0D0:hp_outs=1 (0x1b/0x0/0x0/0x0/0x0) May 18 21:04:31 sidpc kernel: snd_hda_codec_realtek hdaudioC0D0:mono: mono_out=0x0 May 18 21:04:31 sidpc kernel: snd_hda_codec_realtek hdaudioC0D0: dig-out=0x11/0x1e May 18 21:04:31 sidpc kernel: snd_hda_codec_realtek hdaudioC0D0:inputs: May 18 21:04:31 sidpc kernel: snd_hda_codec_realtek hdaudioC0D0: Front Mic=0x19 May 18 21:04:31 sidpc kernel: snd_hda_codec_realtek hdaudioC0D0: Rear Mic=0x18 May 18 21:04:31 sidpc kernel: snd_hda_codec_realtek hdaudioC0D0: Line=0x1a And the fact that i915 is mentioned makes me think it's the HDMI or DisplayPort monitor confusing the system into reconfiguring audio. ** Package changed: pulseaudio (Ubuntu) => linux (Ubuntu) -- 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/1879182 Title: Sound cuts off and back on randomly during online streaming of videos Status in linux package in Ubuntu: Incomplete Bug description: Sound shuts off and turns back on again with two pop clicks. When the sound is off, if i turn up the volume to the max, i can hear crackling sound in speakers in tune with sound playing on the computer. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: pulseaudio 1:13.99.1-1ubuntu3.2 ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30 Uname: Linux 5.4.0-29-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: siddahuja 31829 F pulseaudio /dev/snd/controlC0: siddahuja 31829 F pulseaudio /dev/snd/pcmC0D0p: siddahuja 31829 F...m pulseaudio /dev/snd/timer: siddahuja 31829 f pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sun May 17 23:56:27 2020 InstallationDate: Installed on 2020-04-27 (20 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/20/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F4 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: Z170X-Gaming 3 dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF4:bd10/20/2015:svnGigabyteTechnologyCo.,Ltd.:pnZ170X-Gaming3:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnZ170X-Gaming3:rvrx.x:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: Z170X-Gaming 3 dmi.product.sku: To be filled by O.E.M. dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: Gigabyte Technology Co., Ltd. modified.conffile..etc.pulse.default.pa: [modified] mtime.conffile..etc.pulse.default.pa: 2020-05-17T19:59:02.590821 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1879182/+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 1341256] Re: Press caps lock on Apple wireless keyboard and the keyboard stops working
** Summary changed: - Press caps lock on bluetooth keyboard then the keyboard go death + Press caps lock on Apple wireless keyboard and the keyboard stops working -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1341256 Title: Press caps lock on Apple wireless keyboard and the keyboard stops working Status in bluez package in Ubuntu: Confirmed Status in linux package in Ubuntu: Confirmed Bug description: I am typing using the Apple wireless keyboard,When I press 'caps lock',the keyboard don't work any more! So I go use keyboard on the Macbook.The key case have change,but the light on the key do not light on. I have to off the bluetooth then make it on again.Then reconnect the wireless keyboard. Yes,It work again. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: bluez 4.101-0ubuntu13 ProcVersionSignature: Ubuntu 3.16.0-3.8-generic 3.16.0-rc4 Uname: Linux 3.16.0-3-generic x86_64 NonfreeKernelModules: wl nvidia ApportVersion: 2.14.1-0ubuntu3.2 Architecture: amd64 CurrentDesktop: Unity Date: Sun Jul 13 17:12:23 2014 InstallationDate: Installed on 2014-03-08 (126 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Alpha amd64 (20140307) InterestingModules: bnep rfcomm btusb bluetooth MachineType: Apple Inc. MacBookPro9,1 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-3-generic.efi.signed root=UUID=6510f595-2f49-4798-953a-ed186346c60d ro irqpoll SourcePackage: bluez UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/08/2012 dmi.bios.vendor: Apple Inc. dmi.bios.version: MBP91.88Z.00D3.B08.1208081132 dmi.board.asset.tag: Base Board Asset Tag# dmi.board.name: Mac-4B7AC7E43945597E dmi.board.vendor: Apple Inc. dmi.board.version: MacBookPro9,1 dmi.chassis.type: 10 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-4B7AC7E43945597E dmi.modalias: dmi:bvnAppleInc.:bvrMBP91.88Z.00D3.B08.1208081132:bd08/08/2012:svnAppleInc.:pnMacBookPro9,1:pvr1.0:rvnAppleInc.:rnMac-4B7AC7E43945597E:rvrMacBookPro9,1:cvnAppleInc.:ct10:cvrMac-4B7AC7E43945597E: dmi.product.name: MacBookPro9,1 dmi.product.version: 1.0 dmi.sys.vendor: Apple Inc. hciconfig: hci0:Type: BR/EDR Bus: USB BD Address: 7C:D1:C3:79:A7:25 ACL MTU: 1021:8 SCO MTU: 64:1 UP RUNNING PSCAN RX bytes:119665 acl:5720 sco:0 events:2443 errors:0 TX bytes:13420 acl:640 sco:0 commands:718 errors:0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1341256/+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 1852016] Re: Applications delayed on launch
Found it after modifying the web search a little. I had to start openbox
with:
/usr/bin/dbus-launch --exit-with-session openbox --startup
$HOME/.config/openbox/autostart
The dbus-launch --exit-with-session apparently starts some service that
gnome apps now insist on. This apparently works with other window
managers: it was an i3 user who found it.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to dbus in Ubuntu.
https://bugs.launchpad.net/bugs/1852016
Title:
Applications delayed on launch
Status in dbus package in Ubuntu:
Confirmed
Bug description:
Hello,
i am unsure if this is really a problem with dbus but my first
research showed it could be related to dbus.
1.)
No LSB modules are available.
Distributor ID: Ubuntu
Description: Ubuntu 19.10
Release: 19.10
Codename: eoan
Ubuntu Budgie on T460 with 256GB SSD and 16GB RAM
2.)
dbus:
Installed: 1.12.14-1ubuntu2
Candidate: 1.12.14-1ubuntu2
Version table:
*** 1.12.14-1ubuntu2 500
500 http://de.archive.ubuntu.com/ubuntu eoan/main amd64 Packages
100 /var/lib/dpkg/status
3.) I've expected just "normal" loading applications
4.) Some applications are delayed at startup. The application will
take around 30s to launch, but afterwards it just runs fine. Affected
application I found so far are KeepassXC, Filezilla and OnlyOffice
Desktop-Editor. From strace I saw this applications are stopping (for
about 20-30s) at this point:
connect(12, {sa_family=AF_UNIX, sun_path="/run/user/1000/bus"}, 110) = 0
getpid()= 8165
geteuid() = 1000
getegid() = 1000
getpid()= 8165
geteuid() = 1000
getegid() = 1000
sendmsg(12, {msg_name=NULL, msg_namelen=0, msg_iov=[{iov_base="\0",
iov_len=1}], msg_iovlen=1, msg_control=[{cmsg_len=28, cmsg_level=SOL_SOCKET,
cmsg_type=SCM_CREDENTIALS, cmsg_data={pid=8165, uid=1000, gid=1000}}],
msg_controllen=32, msg_flags=0}, MSG_NOSIGNAL) = 1
sendto(12, "AUTH\r\n", 6, MSG_NOSIGNAL, NULL, 0) = 6
recvfrom(12, "REJECTED EXTERNAL\r\n", 4096, 0, NULL, NULL) = 19
sendto(12, "AUTH EXTERNAL 31303030\r\n", 24, MSG_NOSIGNAL, NULL, 0) = 24
recvfrom(12, "OK 7f079149c4e5e774135107445dc85"..., 4096, 0, NULL, NULL) = 37
sendto(12, "NEGOTIATE_UNIX_FD\r\n", 19, MSG_NOSIGNAL, NULL, 0) = 19
recvfrom(12, "AGREE_UNIX_FD\r\n", 4096, 0, NULL, NULL) = 15
sendto(12, "BEGIN\r\n", 7, MSG_NOSIGNAL, NULL, 0) = 7
write(15, "\1\0\0\0\0\0\0\0", 8)= 8
eventfd2(0, EFD_CLOEXEC|EFD_NONBLOCK) = 14
write(14, "\1\0\0\0\0\0\0\0", 8)= 8
write(15, "\1\0\0\0\0\0\0\0", 8)= 8
poll([{fd=14, events=POLLIN}], 1, 25000) = 1 ([{fd=14, revents=POLLIN}])
read(14, "\1\0\0\0\0\0\0\0", 16)= 8
poll([{fd=14, events=POLLIN}], 1, 25000
During my first research I found this following to topics related to the
issue:
https://askubuntu.com/questions/1184774/some-applications-on-ubuntu-19-10-very-slow-to-start
This Stackoverflow topic links to the archlinux forum:
https://bbs.archlinux.org/viewtopic.php?id=230036
I can confirm that running the delayed applications with "dbus-launch
--exit-with-session application" or by running it as root they are all
starting without any delay.
Thanks for your help! Let me know if you need any further information.
Best Regards,
Sebastian
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/dbus/+bug/1852016/+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 1852016] Re: Applications delayed on launch
Two other apps that show the problem: pavucontrol and cheese.
I'm using the openbox window manager. I assume the apps are looking for some
sort of reply that a gnome desktop would give them.
In strace, it's waiting on:
poll([{fd=15, events=POLLIN}], 1, 25000)
(the fd 15 for cheese, 11 for pavucontrol).
If I run journalctl -b 0 while pavucontrol is waiting to start, I get
the attached log: I've edited it to show the end of one run of
pavucontrol and then a second run up to the point where it hangs (with
comments interspersed by me). At the end of the previous run, after I
hit ^C, it prints
Failed to create file chooser proxy: Error calling StartServiceByName
for org.freedesktop.impl.portal.desktop.gtk: Timeout was reached
A web search for that message gives a gazillion hits -- lots of people
are seeing this -- but so far I haven't found a solution/workaround.
** Attachment added: "journalctl -b 0 from two sucessive runs of pavucontrol"
https://bugs.launchpad.net/ubuntu/+source/dbus/+bug/1852016/+attachment/5373818/+files/journalctl.b.0.txt
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to dbus in Ubuntu.
https://bugs.launchpad.net/bugs/1852016
Title:
Applications delayed on launch
Status in dbus package in Ubuntu:
Confirmed
Bug description:
Hello,
i am unsure if this is really a problem with dbus but my first
research showed it could be related to dbus.
1.)
No LSB modules are available.
Distributor ID: Ubuntu
Description: Ubuntu 19.10
Release: 19.10
Codename: eoan
Ubuntu Budgie on T460 with 256GB SSD and 16GB RAM
2.)
dbus:
Installed: 1.12.14-1ubuntu2
Candidate: 1.12.14-1ubuntu2
Version table:
*** 1.12.14-1ubuntu2 500
500 http://de.archive.ubuntu.com/ubuntu eoan/main amd64 Packages
100 /var/lib/dpkg/status
3.) I've expected just "normal" loading applications
4.) Some applications are delayed at startup. The application will
take around 30s to launch, but afterwards it just runs fine. Affected
application I found so far are KeepassXC, Filezilla and OnlyOffice
Desktop-Editor. From strace I saw this applications are stopping (for
about 20-30s) at this point:
connect(12, {sa_family=AF_UNIX, sun_path="/run/user/1000/bus"}, 110) = 0
getpid()= 8165
geteuid() = 1000
getegid() = 1000
getpid()= 8165
geteuid() = 1000
getegid() = 1000
sendmsg(12, {msg_name=NULL, msg_namelen=0, msg_iov=[{iov_base="\0",
iov_len=1}], msg_iovlen=1, msg_control=[{cmsg_len=28, cmsg_level=SOL_SOCKET,
cmsg_type=SCM_CREDENTIALS, cmsg_data={pid=8165, uid=1000, gid=1000}}],
msg_controllen=32, msg_flags=0}, MSG_NOSIGNAL) = 1
sendto(12, "AUTH\r\n", 6, MSG_NOSIGNAL, NULL, 0) = 6
recvfrom(12, "REJECTED EXTERNAL\r\n", 4096, 0, NULL, NULL) = 19
sendto(12, "AUTH EXTERNAL 31303030\r\n", 24, MSG_NOSIGNAL, NULL, 0) = 24
recvfrom(12, "OK 7f079149c4e5e774135107445dc85"..., 4096, 0, NULL, NULL) = 37
sendto(12, "NEGOTIATE_UNIX_FD\r\n", 19, MSG_NOSIGNAL, NULL, 0) = 19
recvfrom(12, "AGREE_UNIX_FD\r\n", 4096, 0, NULL, NULL) = 15
sendto(12, "BEGIN\r\n", 7, MSG_NOSIGNAL, NULL, 0) = 7
write(15, "\1\0\0\0\0\0\0\0", 8)= 8
eventfd2(0, EFD_CLOEXEC|EFD_NONBLOCK) = 14
write(14, "\1\0\0\0\0\0\0\0", 8)= 8
write(15, "\1\0\0\0\0\0\0\0", 8)= 8
poll([{fd=14, events=POLLIN}], 1, 25000) = 1 ([{fd=14, revents=POLLIN}])
read(14, "\1\0\0\0\0\0\0\0", 16)= 8
poll([{fd=14, events=POLLIN}], 1, 25000
During my first research I found this following to topics related to the
issue:
https://askubuntu.com/questions/1184774/some-applications-on-ubuntu-19-10-very-slow-to-start
This Stackoverflow topic links to the archlinux forum:
https://bbs.archlinux.org/viewtopic.php?id=230036
I can confirm that running the delayed applications with "dbus-launch
--exit-with-session application" or by running it as root they are all
starting without any delay.
Thanks for your help! Let me know if you need any further information.
Best Regards,
Sebastian
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/dbus/+bug/1852016/+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 1879352] Re: /usr/bin/im-launch i3 fails
I was able to fix this by changing ``` exec $STARTUP ``` to ``` $STARTUP ``` Interestingly, this doesn't leave a shell process running -- it leaves `gdm-x-session` running. So perhaps that is emulating a shell somehow, but gets the unquoting wrong for `exec`? -- 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/1879352 Title: /usr/bin/im-launch i3 fails Status in xorg package in Ubuntu: New Bug description: Trying to run i3 in Focal Fossa, login fails. The screen goes black briefly, then returns to the login screen. I expect this is reproducible by just installing `i3`, selecting it on the settings in the login screen, and logging in. I see the following in the log: ``` May 18 11:32:21 hopper /usr/lib/gdm3/gdm-x-session[4733]: /etc/X11/Xsession.d/99x11-common_start: line 5: /usr/bin/im-launch i3: No such file or directory ``` Editing that file to just run `/usr/bin/im-launch i3` works fine. Is this some kind of shell quoting issue, where it's trying to execve that full string? I believe this is in the `x11-common` package: ``` hopper ~ $ dpkg -S /etc/X11/Xsession.d/99x11-common_start x11-common: /etc/X11/Xsession.d/99x11-common_start ``` but Launchpad complains that such a thing does not exist. Perhaps I misunderstand "package". To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1879352/+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 1879421] Re: package initramfs-tools 0.133ubuntu10 failed to install/upgrade: installed initramfs-tools package post-installation script subprocess returned error exit status 1
** Attachment added: "Dmesg.txt" https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1879421/+attachment/5373805/+files/Dmesg.txt -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/1879421 Title: package initramfs-tools 0.133ubuntu10 failed to install/upgrade: installed initramfs-tools package post-installation script subprocess returned error exit status 1 Status in initramfs-tools package in Ubuntu: New Bug description: Low disk space in /var/tmp mount causes post-installation script to fail. It should probably detect it. ProblemType: Package DistroRelease: Ubuntu 19.10 Package: initramfs-tools 0.133ubuntu10 ProcVersionSignature: Ubuntu 5.3.0-1023.25-raspi2 5.3.18 Uname: Linux 5.3.0-1023-raspi2 aarch64 ApportVersion: 2.20.11-0ubuntu8.8 Architecture: arm64 Date: Tue May 19 00:23:34 2020 ErrorMessage: installed initramfs-tools package post-installation script subprocess returned error exit status 1 PackageArchitecture: all Python3Details: /usr/bin/python3.7, Python 3.7.5, python3-minimal, 3.7.5-1 PythonDetails: /usr/bin/python2.7, Python 2.7.17, python-minimal, 2.7.17-1 RelatedPackageVersions: dpkg 1.19.7ubuntu2 apt 1.9.4ubuntu0.1 SourcePackage: initramfs-tools Title: package initramfs-tools 0.133ubuntu10 failed to install/upgrade: installed initramfs-tools package post-installation script subprocess returned error exit status 1 UpgradeStatus: Upgraded to eoan on 2020-05-19 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1879421/+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 1879421] Re: package initramfs-tools 0.133ubuntu10 failed to install/upgrade: installed initramfs-tools package post-installation script subprocess returned error exit status 1
** Tags removed: need-duplicate-check -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/1879421 Title: package initramfs-tools 0.133ubuntu10 failed to install/upgrade: installed initramfs-tools package post-installation script subprocess returned error exit status 1 Status in initramfs-tools package in Ubuntu: New Bug description: Low disk space in /var/tmp mount causes post-installation script to fail. It should probably detect it. ProblemType: Package DistroRelease: Ubuntu 19.10 Package: initramfs-tools 0.133ubuntu10 ProcVersionSignature: Ubuntu 5.3.0-1023.25-raspi2 5.3.18 Uname: Linux 5.3.0-1023-raspi2 aarch64 ApportVersion: 2.20.11-0ubuntu8.8 Architecture: arm64 Date: Tue May 19 00:23:34 2020 ErrorMessage: installed initramfs-tools package post-installation script subprocess returned error exit status 1 PackageArchitecture: all Python3Details: /usr/bin/python3.7, Python 3.7.5, python3-minimal, 3.7.5-1 PythonDetails: /usr/bin/python2.7, Python 2.7.17, python-minimal, 2.7.17-1 RelatedPackageVersions: dpkg 1.19.7ubuntu2 apt 1.9.4ubuntu0.1 SourcePackage: initramfs-tools Title: package initramfs-tools 0.133ubuntu10 failed to install/upgrade: installed initramfs-tools package post-installation script subprocess returned error exit status 1 UpgradeStatus: Upgraded to eoan on 2020-05-19 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1879421/+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 1879421] [NEW] package initramfs-tools 0.133ubuntu10 failed to install/upgrade: installed initramfs-tools package post-installation script subprocess returned error exit status 1
Public bug reported: Low disk space in /var/tmp mount causes post-installation script to fail. It should probably detect it. ProblemType: Package DistroRelease: Ubuntu 19.10 Package: initramfs-tools 0.133ubuntu10 ProcVersionSignature: Ubuntu 5.3.0-1023.25-raspi2 5.3.18 Uname: Linux 5.3.0-1023-raspi2 aarch64 ApportVersion: 2.20.11-0ubuntu8.8 Architecture: arm64 Date: Tue May 19 00:23:34 2020 ErrorMessage: installed initramfs-tools package post-installation script subprocess returned error exit status 1 PackageArchitecture: all Python3Details: /usr/bin/python3.7, Python 3.7.5, python3-minimal, 3.7.5-1 PythonDetails: /usr/bin/python2.7, Python 2.7.17, python-minimal, 2.7.17-1 RelatedPackageVersions: dpkg 1.19.7ubuntu2 apt 1.9.4ubuntu0.1 SourcePackage: initramfs-tools Title: package initramfs-tools 0.133ubuntu10 failed to install/upgrade: installed initramfs-tools package post-installation script subprocess returned error exit status 1 UpgradeStatus: Upgraded to eoan on 2020-05-19 (0 days ago) ** Affects: initramfs-tools (Ubuntu) Importance: Undecided Status: New ** Tags: apport-package arm64 eoan third-party-packages uec-images ** Attachment removed: "Dmesg.txt" https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1879421/+attachment/5373800/+files/Dmesg.txt -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/1879421 Title: package initramfs-tools 0.133ubuntu10 failed to install/upgrade: installed initramfs-tools package post-installation script subprocess returned error exit status 1 Status in initramfs-tools package in Ubuntu: New Bug description: Low disk space in /var/tmp mount causes post-installation script to fail. It should probably detect it. ProblemType: Package DistroRelease: Ubuntu 19.10 Package: initramfs-tools 0.133ubuntu10 ProcVersionSignature: Ubuntu 5.3.0-1023.25-raspi2 5.3.18 Uname: Linux 5.3.0-1023-raspi2 aarch64 ApportVersion: 2.20.11-0ubuntu8.8 Architecture: arm64 Date: Tue May 19 00:23:34 2020 ErrorMessage: installed initramfs-tools package post-installation script subprocess returned error exit status 1 PackageArchitecture: all Python3Details: /usr/bin/python3.7, Python 3.7.5, python3-minimal, 3.7.5-1 PythonDetails: /usr/bin/python2.7, Python 2.7.17, python-minimal, 2.7.17-1 RelatedPackageVersions: dpkg 1.19.7ubuntu2 apt 1.9.4ubuntu0.1 SourcePackage: initramfs-tools Title: package initramfs-tools 0.133ubuntu10 failed to install/upgrade: installed initramfs-tools package post-installation script subprocess returned error exit status 1 UpgradeStatus: Upgraded to eoan on 2020-05-19 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1879421/+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 1879402] Re: Proper monitor resolution/refresh rate not available
** Package changed: ubuntu => xorg (Ubuntu) -- 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/1879402 Title: Proper monitor resolution/refresh rate not available Status in xorg package in Ubuntu: New Bug description: I'm currently (in Ubuntu 20.04) stuck with this low resolution: 640x480 59.94*, what I want to have is the monitor specs: 1080p and 144 Hz. This problem appeared after plugging in my old monitor after 2 years again, it's a philips 272g. Things that I unsuccesfully tried to get a proper resolution: -Use different GPUs from different vendors: 1050 ti and 5700 xt. Use different drivers: propritary and open source -Change resolution via xrandr addmode/newmode (leads to "no signal" from monitor) -Using "GRUB_GFXMODE" config in grub (no change) -Searching through logs, only useleful thing I found was in the Xorg log: [12.117] (II) AMDGPU(0): EDID for output DisplayPort-0 [12.117] (II) AMDGPU(0): Printing probed modes for output DisplayPort-0 [12.117] (II) AMDGPU(0): Modeline "640x480"x59.9 25.18 640 656 752 800 480 490 492 525 -hsync -vsync (31.5 kHz e) -In Windows the resolution works fine -Both GPUs work fine with a different monitor I'm not sure how to proceed here nor do I know where the problem lies. I assume this to be a bug in Ubuntu because a bunch of different GPUs/drivers lead to this problem making it unlikely to be a driver problem. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 Uname: Linux 5.4.0-050400-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Mon May 18 22:16:58 2020 DistUpgraded: 2020-05-09 15:39:17,760 ERROR got error from PostInstallScript ./xorg_fix_proprietary.py (g-exec-error-quark: Failed to execute child process “./xorg_fix_proprietary.py” (No such file or directory) (8)) DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Navi 10 [Radeon RX 5600 OEM/5600 XT / 5700/5700 XT] [1002:731f] (rev c1) (prog-if 00 [VGA controller]) Subsystem: Advanced Micro Devices, Inc. [AMD/ATI] Navi 10 [Radeon RX 5600 OEM/5600 XT / 5700/5700 XT] [1002:0b36] InstallationDate: Installed on 2019-11-26 (173 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: Micro-Star International Co., Ltd. MS-7A34 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-050400-generic root=UUID=f3ec722e-f50e-43cf-8e55-3cbdb22a0592 ro drm.debug=0xe plymouth:debug SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to focal on 2020-05-09 (9 days ago) dmi.bios.date: 11/29/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: A.LQ dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: B350 PC MATE (MS-7A34) dmi.board.vendor: Micro-Star International Co., Ltd. dmi.board.version: 2.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: 2.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrA.LQ:bd11/29/2019:svnMicro-StarInternationalCo.,Ltd.:pnMS-7A34:pvr2.0:rvnMicro-StarInternationalCo.,Ltd.:rnB350PCMATE(MS-7A34):rvr2.0:cvnMicro-StarInternationalCo.,Ltd.:ct3:cvr2.0: dmi.product.family: To be filled by O.E.M. dmi.product.name: MS-7A34 dmi.product.sku: To be filled by O.E.M. dmi.product.version: 2.0 dmi.sys.vendor: Micro-Star International Co., Ltd. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101+git2005070630.c997ba~oibaf~f version.libgl1-mesa-dri: libgl1-mesa-dri 20.2~git2005181337.b5accb~oibaf~f version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2 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: Tue Nov 26 22:01:15 2019 xserver.configfile: default xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.20.5+git20191008-0ubuntu1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1879402/+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 1879402] [NEW] Proper monitor resolution/refresh rate not available
You have been subscribed to a public bug: I'm currently (in Ubuntu 20.04) stuck with this low resolution: 640x480 59.94*, what I want to have is the monitor specs: 1080p and 144 Hz. This problem appeared after plugging in my old monitor after 2 years again, it's a philips 272g. Things that I unsuccesfully tried to get a proper resolution: -Use different GPUs from different vendors: 1050 ti and 5700 xt. Use different drivers: propritary and open source -Change resolution via xrandr addmode/newmode (leads to "no signal" from monitor) -Using "GRUB_GFXMODE" config in grub (no change) -Searching through logs, only useleful thing I found was in the Xorg log: [12.117] (II) AMDGPU(0): EDID for output DisplayPort-0 [12.117] (II) AMDGPU(0): Printing probed modes for output DisplayPort-0 [12.117] (II) AMDGPU(0): Modeline "640x480"x59.9 25.18 640 656 752 800 480 490 492 525 -hsync -vsync (31.5 kHz e) -In Windows the resolution works fine -Both GPUs work fine with a different monitor I'm not sure how to proceed here nor do I know where the problem lies. I assume this to be a bug in Ubuntu because a bunch of different GPUs/drivers lead to this problem making it unlikely to be a driver problem. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 Uname: Linux 5.4.0-050400-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Mon May 18 22:16:58 2020 DistUpgraded: 2020-05-09 15:39:17,760 ERROR got error from PostInstallScript ./xorg_fix_proprietary.py (g-exec-error-quark: Failed to execute child process “./xorg_fix_proprietary.py” (No such file or directory) (8)) DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Navi 10 [Radeon RX 5600 OEM/5600 XT / 5700/5700 XT] [1002:731f] (rev c1) (prog-if 00 [VGA controller]) Subsystem: Advanced Micro Devices, Inc. [AMD/ATI] Navi 10 [Radeon RX 5600 OEM/5600 XT / 5700/5700 XT] [1002:0b36] InstallationDate: Installed on 2019-11-26 (173 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: Micro-Star International Co., Ltd. MS-7A34 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-050400-generic root=UUID=f3ec722e-f50e-43cf-8e55-3cbdb22a0592 ro drm.debug=0xe plymouth:debug SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to focal on 2020-05-09 (9 days ago) dmi.bios.date: 11/29/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: A.LQ dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: B350 PC MATE (MS-7A34) dmi.board.vendor: Micro-Star International Co., Ltd. dmi.board.version: 2.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: 2.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrA.LQ:bd11/29/2019:svnMicro-StarInternationalCo.,Ltd.:pnMS-7A34:pvr2.0:rvnMicro-StarInternationalCo.,Ltd.:rnB350PCMATE(MS-7A34):rvr2.0:cvnMicro-StarInternationalCo.,Ltd.:ct3:cvr2.0: dmi.product.family: To be filled by O.E.M. dmi.product.name: MS-7A34 dmi.product.sku: To be filled by O.E.M. dmi.product.version: 2.0 dmi.sys.vendor: Micro-Star International Co., Ltd. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101+git2005070630.c997ba~oibaf~f version.libgl1-mesa-dri: libgl1-mesa-dri 20.2~git2005181337.b5accb~oibaf~f version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2 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: Tue Nov 26 22:01:15 2019 xserver.configfile: default xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.20.5+git20191008-0ubuntu1 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal resolution third-party-packages ubuntu -- Proper monitor resolution/refresh rate not available https://bugs.launchpad.net/bugs/1879402 You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg 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 1879150] Re: apport-kde shows 'text' instead of text in message box
This bug was fixed in the package apport - 2.20.11-0ubuntu35 --- apport (2.20.11-0ubuntu35) groovy; urgency=medium * kde/apport-kde: Stop showing 'text' instead of a useful string. Thanks to Launchpad user Niklas Sombert for the patch. (LP: #1879150) -- Brian Murray Mon, 18 May 2020 10:28:25 -0700 ** Changed in: apport (Ubuntu) Status: In Progress => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/1879150 Title: apport-kde shows 'text' instead of text in message box Status in apport package in Ubuntu: Fix Released Status in apport source package in Xenial: Confirmed Status in apport source package in Bionic: New Status in apport source package in Eoan: New Status in apport source package in Focal: Triaged Bug description: I had some other software crashing and wanting to report a bug, Apport displayed a pretty nonsensical message box (see the screenshot). $ lsb_release -rd Description:Ubuntu 20.04 LTS Release:20.04 $ apt-cache policy apport-kde apport-kde: Installed: 2.20.11-0ubuntu27 Candidate: 2.20.11-0ubuntu27 Version table: *** 2.20.11-0ubuntu27 500 500 http://de.archive.ubuntu.com/ubuntu focal/universe amd64 Packages 500 http://de.archive.ubuntu.com/ubuntu focal/universe i386 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: apport-kde 2.20.11-0ubuntu27 ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30 Uname: Linux 5.4.0-29-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: KDE Date: Sun May 17 14:11:30 2020 InstallationDate: Installed on 2015-12-11 (1618 days ago) InstallationMedia: Kubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805) PackageArchitecture: all SourcePackage: apport UpgradeStatus: Upgraded to focal on 2020-05-15 (1 days ago) mtime.conffile..etc.apport.crashdb.conf: 2019-11-21T10:33:51.640107 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1879150/+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
Re: [Touch-packages] [Bug 1877987] Re: apt search coredumping
Sir, My has been crushed about over one month with the google, I think... CA is cannot reboot... Thank you... On Mon, May 18, 2020, 4:35 PM Julian Andres Klode < julian.kl...@canonical.com> wrote: > Fixed in 2.1.3, will look into adding a test case and backporting this > to 2.0 shortly. > > ** Changed in: apt (Ubuntu) >Status: New => Fix Committed > > ** Also affects: apt (Ubuntu Bionic) >Importance: Undecided >Status: New > > ** Also affects: apt (Ubuntu Focal) >Importance: Undecided >Status: New > > ** No longer affects: apt (Ubuntu Bionic) > > ** Changed in: apt (Ubuntu Focal) >Status: New => Triaged > > -- > You received this bug notification because you are subscribed to apt in > Ubuntu. > Matching subscriptions: dragonhahney > https://bugs.launchpad.net/bugs/1877987 > > Title: > apt search coredumping > > Status in apt package in Ubuntu: > Fix Committed > Status in apt source package in Focal: > Triaged > > Bug description: > root@citoyx:/var/crash# apt search jdk > Sorting... Done > Segmentation fault (core dumped) > > May 11 12:34:25 citoyx kernel: [ 1354.337907] apt[10418]: segfault at > 7f67292dcfc0 ip 7f6309ce4997 sp 7ffdab880930 error 4 in > libapt-pkg.so.6.0.0[7f6309bb5000+147000] > May 11 12:34:25 citoyx kernel: [ 1354.337916] Code: 48 8b 45 18 48 8b 04 > d0 48 83 c4 08 5b 5d c3 0f 1f 40 00 f3 0f 1e fa 55 48 89 fd 53 48 89 f3 48 > 83 ec 08 48 8b 06 48 8b 4e 08 <8b> 10 48 8d 04 d5 00 00 00 00 48 29 d0 48 > 8b 51 60 48 8d 04 c2 0f > > > root@citoyx:/var/crash# cat /etc/lsb-release > DISTRIB_ID=Ubuntu > DISTRIB_RELEASE=20.04 > DISTRIB_CODENAME=focal > DISTRIB_DESCRIPTION="Ubuntu 20.04 LTS" > > > apt search is coredumping > While apt install/upgrade/update is running fine > > crash file in attachment. > > To manage notifications about this bug go to: > https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1877987/+subscriptions > -- 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/1877987 Title: apt search coredumping Status in apt package in Ubuntu: Fix Committed Status in apt source package in Focal: Triaged Bug description: root@citoyx:/var/crash# apt search jdk Sorting... Done Segmentation fault (core dumped) May 11 12:34:25 citoyx kernel: [ 1354.337907] apt[10418]: segfault at 7f67292dcfc0 ip 7f6309ce4997 sp 7ffdab880930 error 4 in libapt-pkg.so.6.0.0[7f6309bb5000+147000] May 11 12:34:25 citoyx kernel: [ 1354.337916] Code: 48 8b 45 18 48 8b 04 d0 48 83 c4 08 5b 5d c3 0f 1f 40 00 f3 0f 1e fa 55 48 89 fd 53 48 89 f3 48 83 ec 08 48 8b 06 48 8b 4e 08 <8b> 10 48 8d 04 d5 00 00 00 00 48 29 d0 48 8b 51 60 48 8d 04 c2 0f root@citoyx:/var/crash# cat /etc/lsb-release DISTRIB_ID=Ubuntu DISTRIB_RELEASE=20.04 DISTRIB_CODENAME=focal DISTRIB_DESCRIPTION="Ubuntu 20.04 LTS" apt search is coredumping While apt install/upgrade/update is running fine crash file in attachment. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1877987/+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 1423796] Re: Unable to mount lvmcache root device at boot time
Still a problem in 20.04... -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lvm2 in Ubuntu. https://bugs.launchpad.net/bugs/1423796 Title: Unable to mount lvmcache root device at boot time Status in initramfs-tools package in Ubuntu: Confirmed Status in linux package in Ubuntu: Confirmed Status in lvm2 package in Ubuntu: Confirmed Bug description: I'm experimenting with Vivid Vervet on a virtual machine and tried a new LVM feature, lvmcache. I made a cache for the root file system, rebuilt the initrd and rebooted the VM. At boot time, the system failed to activate the root LV. After some investigation, I found out, it's because the initrd is missing some essential stuff needed for activating a cached LV. The initrd was missing the dm-cache module. I regenerated the initrd with explicitly listing dm-cache in /etc/initramfs-tools/modules, but the system still can't boot up, because now it is missing the /usr/sbin/cache_check utility. As SSDs are becoming more and more common, I think it will be common to use them as cache for root file systems, thus it is mandatory to make sure that an initrd can mount an lvmcached root device when necessary, preferably without /etc/initramfs-tools/modules and other manual initrd hacking. System details: Linux lvmvm 3.18.0-13-generic #14-Ubuntu SMP Fri Feb 6 09:55:14 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux Distributor ID: Ubuntu Description: Ubuntu Vivid Vervet (development branch) Release: 15.04 Codename: vivid LVM version: 2.02.111(2) (2014-09-01) Library version: 1.02.90 (2014-09-01) Driver version: 4.28.0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1423796/+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 1854355] Re: LUKS partition on LVM has wrong device name
I'm seeing the same behavior. Changing nvme0n1p3_crypt to nvme1n1p3_crypt in /etc/crypttab (in the hope of aligning the naming convention with the underlying NVME device files) and running: # dmsetup rename nvme0n1p3_crypt nvme1n1p3_crypt # update-initramfs -c -t -k all # update-grub # reboot will flip things around. The NVME device and its partitions will now be nvme0n1pX on the next reboot while the LUKS device will be on nvme1n1p3_crypt. Each time I rename the LUKS device the underlying devices will flip around as well and never end up having the same naming convention. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lvm2 in Ubuntu. https://bugs.launchpad.net/bugs/1854355 Title: LUKS partition on LVM has wrong device name Status in lvm2 package in Ubuntu: Confirmed Bug description: Ubuntu release: Ubuntu Desktop 18.04.2 LTS Kernel: 5.0.0-36-generic Storage devices: two NVMe SSDs (1TB and 512GB) Ubuntu Desktop install – selected the options to use disk encryption and LVM The largest disk (1TB) is used for the Ubuntu install and this has the device name /dev/nvme0n1 in the Ubiquity installer. Install completes and upon rebooting the operating system asks for the encryption passphrase for the LUKS partition (nvme0n1p3_crypt) which does decrypt as expected. Now when logging in and running lsblk it shows the LUKS partition to be in the wrong place. The 1TB disk now has the name nvme1n1 but the LUKS partition on that disk has the name nvme0n1p3_crypt. Output of lsblk: nvme1n1 259:00 953.9G 0 disk ├─nvme1n1p1 259:10 512M 0 part /boot/efi ├─nvme1n1p2 259:20 732M 0 part /boot └─nvme1n1p3 259:30 952.7G 0 part └─nvme0n1p3_crypt 253:00 952.7G 0 crypt ├─ubuntu--vg-root 253:10 930.4G 0 lvm / └─ubuntu--vg-swap_1 253:20 976M 0 lvm [SWAP] nvme0n1 259:40 477G 0 disk The LUKS partition doesn’t appear to be under nvme0n1p3 but it does on nvme1n1p3 which can be seen when running a luksDump command. Output of luksDump: root@USERPC:~# cryptsetup luksDump /dev/nvme0n1p3 | grep -i "slot 0" Device /dev/nvme0n1p3 doesn't exist or access denied. root@USERPC:~# cryptsetup luksDump /dev/nvme1n1p3 | grep -i "slot 0" Key Slot 0: ENABLED The implications of this so far in my case is not being able to find the correct LUKS partition device name via custom scripts to populate/modify key slots (e.g. 'dmsetup ls' returns the device name nvme0n1p3_crypt). There has not been an issue with Ubuntu decrypting the disk before the login screen. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lvm2/+bug/1854355/+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 1854355] Re: LUKS partition on LVM has wrong device name
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: lvm2 (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lvm2 in Ubuntu. https://bugs.launchpad.net/bugs/1854355 Title: LUKS partition on LVM has wrong device name Status in lvm2 package in Ubuntu: Confirmed Bug description: Ubuntu release: Ubuntu Desktop 18.04.2 LTS Kernel: 5.0.0-36-generic Storage devices: two NVMe SSDs (1TB and 512GB) Ubuntu Desktop install – selected the options to use disk encryption and LVM The largest disk (1TB) is used for the Ubuntu install and this has the device name /dev/nvme0n1 in the Ubiquity installer. Install completes and upon rebooting the operating system asks for the encryption passphrase for the LUKS partition (nvme0n1p3_crypt) which does decrypt as expected. Now when logging in and running lsblk it shows the LUKS partition to be in the wrong place. The 1TB disk now has the name nvme1n1 but the LUKS partition on that disk has the name nvme0n1p3_crypt. Output of lsblk: nvme1n1 259:00 953.9G 0 disk ├─nvme1n1p1 259:10 512M 0 part /boot/efi ├─nvme1n1p2 259:20 732M 0 part /boot └─nvme1n1p3 259:30 952.7G 0 part └─nvme0n1p3_crypt 253:00 952.7G 0 crypt ├─ubuntu--vg-root 253:10 930.4G 0 lvm / └─ubuntu--vg-swap_1 253:20 976M 0 lvm [SWAP] nvme0n1 259:40 477G 0 disk The LUKS partition doesn’t appear to be under nvme0n1p3 but it does on nvme1n1p3 which can be seen when running a luksDump command. Output of luksDump: root@USERPC:~# cryptsetup luksDump /dev/nvme0n1p3 | grep -i "slot 0" Device /dev/nvme0n1p3 doesn't exist or access denied. root@USERPC:~# cryptsetup luksDump /dev/nvme1n1p3 | grep -i "slot 0" Key Slot 0: ENABLED The implications of this so far in my case is not being able to find the correct LUKS partition device name via custom scripts to populate/modify key slots (e.g. 'dmsetup ls' returns the device name nvme0n1p3_crypt). There has not been an issue with Ubuntu decrypting the disk before the login screen. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lvm2/+bug/1854355/+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 1879401] [NEW] [XPS 13 7390 2-in-1, Intel Icelake HDMI, Digital Out, HDMI] sound rarely works
Public bug reported: I have an Ice Lake laptop (Dell 7390 2-in-one) which I am connecting to a TV over HDMI via a Novoo USB-C multiport adapter. This is not a Thunderbolt device, it is just USB-C. It seemed like things used to work fine before I upgraded this system from Ubuntu 19.10 to 20.04, although I couldn't say for certain at this point. But I'm having a ton of difficulty getting audio output over HDMI. Getting it to work requires a lot of retries to reinitialize the device (either by suspending/resuming the laptop, or plugging/unplugging the HDMI cable and/or the multiport adapter). It does work sometimes, but my success rate is very low at this point. Even when it does work, it's brittle: any change to the output port (to speaker and back to HDMI, or from stereo to surround and back) will often break the audio. This fact seems to suggest that the problem doesn't have anything to do with the low-level initialization of the HDMI port; I'd be looking at some mid-layer code. To be clear, there doesn't seem to be any particular symptom, or anything of interest in the logs, other than an absence of sound output. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.6.0-1010.10-oem 5.6.8 Uname: Linux 5.6.0-1010-oem x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: nbryant1510 F pulseaudio /dev/snd/pcmC0D9p: nbryant1510 F...m pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Mon May 18 17:32:11 2020 InstallationDate: Installed on 2020-01-31 (108 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_Jack: Digital Out, HDMI Symptom_PulseAudioLog: May 18 16:36:42 atlantis dbus-daemon[633]: [system] Activating via systemd: service name='org.freedesktop.RealtimeKit1' unit='rtkit-daemon.service' requested by ':1.41' (uid=124 pid=1116 comm="/usr/bin/pulseaudio --daemonize=no --log-target=jo" label="unconfined") May 18 16:36:53 atlantis systemd[1109]: pulseaudio.service: Succeeded. May 18 16:37:03 atlantis systemd[1109]: pulseaudio.socket: Succeeded. Symptom_Type: Sound works for a while, then breaks Title: [XPS 13 7390 2-in-1, Intel Icelake HDMI, Digital Out, HDMI] fails after a while UpgradeStatus: Upgraded to focal on 2020-04-21 (27 days ago) dmi.bios.date: 03/02/2020 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.3.1 dmi.board.name: 06CDVY dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 31 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.3.1:bd03/02/2020:svnDellInc.:pnXPS1373902-in-1:pvr:rvnDellInc.:rn06CDVY:rvrA00:cvnDellInc.:ct31:cvr: dmi.product.family: XPS dmi.product.name: XPS 13 7390 2-in-1 dmi.product.sku: 08B0 dmi.sys.vendor: Dell Inc. ** Affects: alsa-driver (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1879401 Title: [XPS 13 7390 2-in-1, Intel Icelake HDMI, Digital Out, HDMI] sound rarely works Status in alsa-driver package in Ubuntu: New Bug description: I have an Ice Lake laptop (Dell 7390 2-in-one) which I am connecting to a TV over HDMI via a Novoo USB-C multiport adapter. This is not a Thunderbolt device, it is just USB-C. It seemed like things used to work fine before I upgraded this system from Ubuntu 19.10 to 20.04, although I couldn't say for certain at this point. But I'm having a ton of difficulty getting audio output over HDMI. Getting it to work requires a lot of retries to reinitialize the device (either by suspending/resuming the laptop, or plugging/unplugging the HDMI cable and/or the multiport adapter). It does work sometimes, but my success rate is very low at this point. Even when it does work, it's brittle: any change to the output port (to speaker and back to HDMI, or from stereo to surround and back) will often break the audio. This fact seems to suggest that the problem doesn't have anything to do with the low-level initialization of the HDMI port; I'd be looking at some mid-layer code. To be clear, there doesn't seem to be any particular symptom, or anything of interest in the logs, other than an absence of sound output. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.6.0-1010.10-oem 5.6.8 Uname: Linux 5.6.0-1010-oem x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND
[Touch-packages] [Bug 1879326] Re: DNS resolution ceased to work after update
Thank you for your bug report. Could you check in /var/log/dpkg.log what was updated before you started getting the issue? ** Changed in: network-manager (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1879326 Title: DNS resolution ceased to work after update Status in network-manager package in Ubuntu: Incomplete Bug description: Hi I did a Focal install on 14th of May 2020, could work until in the night of 16th of May 2020 and in the morning of the 18th of May 2020 I could not resolve domain names anymore. I can ping DNS servers but the resolution to IP addresses fails. I have switched on automatic installation of security relevant updates. I can reproduce the behaviour with a fresh install accepting all the updates there are. I did not try to find out which update is the cause. See the behaviour below where I even have tried to work around by removing the DNS server of my router: thiemo @ Fujitsu-HO ~ :-( % systemd-resolve --status 20-05-18 12:54 Global LLMNR setting: no MulticastDNS setting: no DNSOverTLS setting: no DNSSEC setting: no DNSSEC supported: no DNSSEC NTA: 10.in-addr.arpa 16.172.in-addr.arpa 168.192.in-addr.arpa 17.172.in-addr.arpa 18.172.in-addr.arpa 19.172.in-addr.arpa 20.172.in-addr.arpa 21.172.in-addr.arpa 22.172.in-addr.arpa 23.172.in-addr.arpa 24.172.in-addr.arpa 25.172.in-addr.arpa 26.172.in-addr.arpa 27.172.in-addr.arpa 28.172.in-addr.arpa 29.172.in-addr.arpa 30.172.in-addr.arpa 31.172.in-addr.arpa corp d.f.ip6.arpa home internal intranet lan local private test Link 2 (enp0s25) Current Scopes: DNS DefaultRoute setting: yes LLMNR setting: yes MulticastDNS setting: no DNSOverTLS setting: no DNSSEC setting: no DNSSEC supported: no DNS Servers: 139.18.25.33 139.18.25.34 77.59.232.36 62.167.241.5 62.2.107.35 62.2.121.84 62.2.121.88 fd00::7eff:4dff:feaa:2528 2001:638:902:1::10 DNS Domain: ~. thiemo @ Fujitsu-HO ~ % host -v myworkspaceinet.post.ch 20-05-18 12:54 Trying "myworkspaceinet.post.ch" ;; connection timed out; no servers could be reached thiemo @ Fujitsu-HO ~ :-( % alias pong 20-05-18 12:55 pong='ping -c3' thiemo @ Fujitsu-HO ~ % pong 139.18.25.33 20-05-18 12:58 PING 139.18.25.33 (139.18.25.33) 56(84) bytes of data. 64 bytes from 139.18.25.33: icmp_seq=1 ttl=246 time=39.9 ms 64 bytes from 139.18.25.33: icmp_seq=2 ttl=246 time=39.0 ms 64 bytes from 139.18.25.33: icmp_seq=3 ttl=246 time=39.4 ms --- 139.18.25.33 ping statistics --- 3 packets transmitted, 3 received, 0% packet loss, time 2003ms rtt min/avg/max/mdev = 39.000/39.431/39.868/0.354 ms Kind regards Thiemo ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: network-manager 1.22.10-1ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30 Uname: Linux 5.4.0-29-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: KDE Date: Mon May 18 13:03:40 2020 InstallationDate: Installed on 2020-05-15 (3 days ago) InstallationMedia: Kubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) IpRoute: default via 192.168.178.1 dev enp0s25 proto dhcp metric 100 169.254.0.0/16 dev enp0s25 scope link metric 1000 192.168.178.0/24 dev enp0s25 proto kernel scope link src 192.168.178.33 metric 100 IwConfig: enp0s25 no wireless extensions. lono wireless extensions. RfKill: SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) nmcli-con: NAMEUUID
[Touch-packages] [Bug 1879282] Re: Workspace shows windows that is not on the current workspace
** Package changed: xorg (Ubuntu) => gnome-shell (Ubuntu) -- 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/1879282 Title: Workspace shows windows that is not on the current workspace Status in gnome-shell package in Ubuntu: New Bug description: If I have two workspaces and have for example firefox on both workspaces, then the second workspace will show the firefox windows that is on the first workspace. I can not controll this window, its just a piece of the background. I get this problem 100% of the time. The way I get it is by being on my second workspace, howering my pointer over the firefox on my topbar, go through the windows of the windows open for firefox, which makes my screen jump to the first window when i hower over the firefox window that is open on the first workspace, to indicate where it is located. Then when i click on the firefox window that is on the second workspace, the window from the first workspace is "stuck" as a wallpaper. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30 Uname: Linux 5.4.0-29-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Mon May 18 10:59:15 2020 DistUpgraded: 2020-04-26 19:27:56,468 DEBUG icon theme changed, re-reading DistroCodename: focal DistroVariant: ubuntu GraphicsCard: Intel Corporation HD Graphics 620 [8086:5916] (rev 02) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. HD Graphics 620 [1043:1740] InstallationDate: Installed on 2020-04-17 (30 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 04f3:0903 Elan Microelectronics Corp. ELAN:Fingerprint Bus 001 Device 003: ID 8087:0a2b Intel Corp. Bus 001 Device 002: ID 0bda:58e4 Realtek Semiconductor Corp. USB2.0 HD UVC WebCam Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: ASUSTeK COMPUTER INC. UX430UA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-29-generic root=UUID=dc6ec013-e29e-4a5e-8dd0-17ae3cf639fc ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to focal on 2020-04-26 (21 days ago) dmi.bios.date: 11/14/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: UX430UA.304 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX430UA dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrUX430UA.304:bd11/14/2017:svnASUSTeKCOMPUTERINC.:pnUX430UA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX430UA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: UX dmi.product.name: UX430UA dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. 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 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 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1879282/+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 1879058] Re: Display viewport incorrect with 90° rotated displayed
Thank you for taking the time to report this bug and helping to make Ubuntu better. Please execute the following command, as it will automatically gather debugging information, in a terminal: apport-collect 1879058 When reporting bugs in the future please use apport by using 'ubuntu- bug' and the name of the package affected. You can learn more about this functionality at https://wiki.ubuntu.com/ReportingBugs. ** Package changed: xorg (Ubuntu) => gnome-shell (Ubuntu) ** Changed in: gnome-shell (Ubuntu) Importance: Undecided => Low ** Changed in: gnome-shell (Ubuntu) Status: New => Incomplete -- 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/1879058 Title: Display viewport incorrect with 90° rotated displayed Status in gnome-shell package in Ubuntu: Incomplete Bug description: The system which automatically configure the position and size of the display seems to not handle the display viewport correctly. When configuring the position of displays with Ubuntu display settings interface, If I set a vertical display (rotated 90°) for a 1920x1080 display, then it seems the viewport or virtual display (I don't really know how you name is) seems to be 1920x1920. So the desktop is bigger than the screen and it can be moved with the mouse. Considering I use multi screens (3 rotated and one normal) it makes some crazy things. So my feeling is that while the screen is rotated, the viewport definition remains 1920x1080 instead of 1080x1920, and the system resolve it by providing a viewport of 1920x1920. This issue can be more or less circumvented using Nvidia Tools to configure displays. With it, the viewport seems to work correctly. However, as soon as a screen is disconnected, the system reconfigure the various displays and the issue comes back. So often, after a sleep or something like that, the issue comes back. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1879058/+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 1870359] Re: My machine as Wi-Fi Hotspot broken after upgrade to 20.04
The log has iptables errors May 18 14:50:08 julep NetworkManager[1050]: [1589806208.0498] Executing: /sbin/iptables --table filter --insert INPUT --in-interface wlp3s0 --protocol tcp --destination-port 53 --jump ACCEPT May 18 14:50:08 julep NetworkManager[1050]: [1589806208.0512] Error executing command: Failed to execute child process “/sbin/iptables†(No such file or directory) Do you have iptables installed? could you do $ which iptables? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1870359 Title: My machine as Wi-Fi Hotspot broken after upgrade to 20.04 Status in network-manager package in Ubuntu: Confirmed Bug description: I have a machine with a wired network connection and a wifi card. I've been using the machine as a wireless router and server in my house. I've attached a screenshot of the Wi-Fi network settings. It looks as expected. Upon updating to 20.04, none of my machines can use the connection. The linux machine will not connect. The windows machine will connect but will not have internet. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: network-manager 1.22.10-1ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.11-0ubuntu22 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Apr 2 15:47:02 2020 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2015-09-30 (1645 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) IpRoute: default via 192.168.0.1 dev eth0 proto static metric 100 169.254.0.0/16 dev eth0 scope link metric 1000 192.168.0.0/24 dev eth0 proto kernel scope link src 192.168.0.100 metric 100 SourcePackage: network-manager UpgradeStatus: Upgraded to focal on 2020-04-02 (0 days ago) WifiSyslog: mtime.conffile..etc.NetworkManager.NetworkManager.conf: 2018-01-13T14:45:42.987041 nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.22.10 connected started full enabled enabled enabled enabled enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1870359/+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 1870359] Re: My machine as Wi-Fi Hotspot broken after upgrade to 20.04
I noticed the iptables needed for the hotspot to work are not set when the hotspot is enabled. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1870359 Title: My machine as Wi-Fi Hotspot broken after upgrade to 20.04 Status in network-manager package in Ubuntu: Confirmed Bug description: I have a machine with a wired network connection and a wifi card. I've been using the machine as a wireless router and server in my house. I've attached a screenshot of the Wi-Fi network settings. It looks as expected. Upon updating to 20.04, none of my machines can use the connection. The linux machine will not connect. The windows machine will connect but will not have internet. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: network-manager 1.22.10-1ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.11-0ubuntu22 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Apr 2 15:47:02 2020 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2015-09-30 (1645 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) IpRoute: default via 192.168.0.1 dev eth0 proto static metric 100 169.254.0.0/16 dev eth0 scope link metric 1000 192.168.0.0/24 dev eth0 proto kernel scope link src 192.168.0.100 metric 100 SourcePackage: network-manager UpgradeStatus: Upgraded to focal on 2020-04-02 (0 days ago) WifiSyslog: mtime.conffile..etc.NetworkManager.NetworkManager.conf: 2018-01-13T14:45:42.987041 nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.22.10 connected started full enabled enabled enabled enabled enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1870359/+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 1876035] Re: Consider making '-o Acquire::Retries=3' the default for 'apt-get update/install/dist-upgrade'
A few points to think about: 1. I am not aware of anyone using that option, we don't know if it works and how it behaves 2. Given 1, what kind of testing can we do? This needs to be thoroughly tested, given that it's not been tested at all. 3. Switching IPs might be useful, but it's not clear to me yet how that would work in practice. We can basically blacklist certain IPs so it jumps to the next one, but we need to make sure we don't run out of IPs I guess. Also we use one connection per hostname, so each failure would switch the connection to a different IP address for all following requests. 4. Does it have any kind of delay right now? I don't think it does, and it sounds hard, and also pointless if we switch IPs. 5. I'd like to retry across different host names too. -- 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/1876035 Title: Consider making '-o Acquire::Retries=3' the default for 'apt-get update/install/dist-upgrade' Status in apt package in Ubuntu: Confirmed Status in apt source package in Groovy: Confirmed Bug description: Hi, We operate archive.ubuntu.com as well as mirrors of it in various places. We're getting reports of various CI/CD jobs failing. Sometimes due to routing issues, issues with overloaded servers/VMs hosting archive, etc. Any chance we can make '-o Acquire::Retries=3' the default for 'apt- get update/install/dist-upgrade'? Preferably with a randomised skew between retries. Also, any chance of having apt-get retry with different IPs/hosts returned from the DNS lookup? (e.g. for archive.ubuntu.com - 91.189.88.142, 91.189.88.152, ...). Thanks. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1876035/+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 1877987] Re: apt search coredumping
Fixed in 2.1.3, will look into adding a test case and backporting this to 2.0 shortly. ** Changed in: apt (Ubuntu) Status: New => Fix Committed ** Also affects: apt (Ubuntu Bionic) Importance: Undecided Status: New ** Also affects: apt (Ubuntu Focal) Importance: Undecided Status: New ** No longer affects: apt (Ubuntu Bionic) ** Changed in: apt (Ubuntu Focal) Status: New => Triaged -- 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/1877987 Title: apt search coredumping Status in apt package in Ubuntu: Fix Committed Status in apt source package in Focal: Triaged Bug description: root@citoyx:/var/crash# apt search jdk Sorting... Done Segmentation fault (core dumped) May 11 12:34:25 citoyx kernel: [ 1354.337907] apt[10418]: segfault at 7f67292dcfc0 ip 7f6309ce4997 sp 7ffdab880930 error 4 in libapt-pkg.so.6.0.0[7f6309bb5000+147000] May 11 12:34:25 citoyx kernel: [ 1354.337916] Code: 48 8b 45 18 48 8b 04 d0 48 83 c4 08 5b 5d c3 0f 1f 40 00 f3 0f 1e fa 55 48 89 fd 53 48 89 f3 48 83 ec 08 48 8b 06 48 8b 4e 08 <8b> 10 48 8d 04 d5 00 00 00 00 48 29 d0 48 8b 51 60 48 8d 04 c2 0f root@citoyx:/var/crash# cat /etc/lsb-release DISTRIB_ID=Ubuntu DISTRIB_RELEASE=20.04 DISTRIB_CODENAME=focal DISTRIB_DESCRIPTION="Ubuntu 20.04 LTS" apt search is coredumping While apt install/upgrade/update is running fine crash file in attachment. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1877987/+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 1879389] [NEW] random freezes and xorg dies sending me back to login screen
Public bug reported: branch new dell xps 2020 machine randomly freezes and xorg dies on me nothing in /var/crash but everything opened, not saved, is lost. i am sent back to login screen. machine has latest bios (1.0.7) is up to date regarding its ubuntu 18.04 i am seeing this in my kern.log which makes me suspect something is wrong with the Intel Iris driver : May 18 22:12:28 asgard kernel: [ 4906.887448] WARN_ON(intel_wait_for_register(dev_priv, regs->driver, (0x1 << ((pw_idx) * 2)), (0x1 << ((pw_idx) * 2)), 1)) May 18 22:12:28 asgard kernel: [ 4906.887524] WARNING: CPU: 2 PID: 5160 at /build/linux-oem-osp1-JJcJwF/linux -oem-osp1-5.0.0/drivers/gpu/drm/i915/intel_runtime_pm.c:308 hsw_wait_for_power_well_enable.isra.8+0x4c/0x50 [ i915] May 18 22:12:28 asgard kernel: [ 4906.887525] Modules linked in: rfcomm ccm cmac bnep uvcvideo btusb btrtl vi deobuf2_vmalloc btbcm videobuf2_memops btintel videobuf2_v4l2 bluetooth videobuf2_common videodev ecdh_generi c media hid_multitouch 8250_dw dell_laptop nls_iso8859_1 intel_rapl x86_pkg_temp_thermal intel_powerclamp cor etemp kvm_intel arc4 snd_hda_codec_hdmi crct10dif_pclmul sof_pci_dev snd_sof_intel_hda_common snd_soc_hdac_hd a snd_sof_intel_hda snd_hda_codec_realtek snd_sof_xtensa_dsp snd_sof crc32_pclmul snd_hda_ext_core snd_hda_co dec_generic snd_soc_acpi_intel_match ledtrig_audio snd_soc_acpi ghash_clmulni_intel snd_soc_core snd_compress ac97_bus snd_pcm_dmaengine snd_hda_intel snd_intel_nhlt snd_hda_codec snd_hda_core snd_hwdep snd_pcm aesni_i ntel snd_seq_midi snd_seq_midi_event snd_rawmidi aes_x86_64 crypto_simd cryptd glue_helper intel_cstate intel _rapl_perf joydev input_leds snd_seq serio_raw dell_wmi iwlmvm dell_smbios snd_seq_device dcdbas idma64 snd_t imer mac80211 virt_dma dell_wmi_descriptor snd May 18 22:12:28 asgard kernel: [ 4906.887547] intel_wmi_thunderbolt wmi_bmof iwlwifi hid_sensor_als soundcor e hid_sensor_trigger industrialio_triggered_buffer kfifo_buf hid_sensor_iio_common mei_me cfg80211 rtsx_pci_m s industrialio mei memstick intel_lpss_pci intel_lpss ucsi_acpi typec_ucsi typec int3403_thermal int340x_ther mal_zone intel_hid mac_hid sparse_keymap int3400_thermal acpi_pad acpi_thermal_rel acpi_tad sch_fq_codel parp ort_pc ppdev lp parport ip_tables x_tables autofs4 btrfs zstd_compress raid10 raid456 async_raid6_recov async _memcpy async_pq async_xor async_tx xor mmc_block raid6_pq libcrc32c raid1 raid0 multipath linear hid_sensor_ hub hid_generic intel_ishtp_hid i915 kvmgt vfio_mdev mdev rtsx_pci_sdmmc vfio_iommu_type1 vfio kvm irqbypass psmouse i2c_algo_bit drm_kms_helper syscopyarea sysfillrect sysimgblt nvme fb_sys_fops drm rtsx_pci nvme_core intel_ish_ipc thunderbolt intel_ishtp i2c_hid wmi hid video pinctrl_icelake pinctrl_intel May 18 22:12:28 asgard kernel: [ 4906.887575] CPU: 2 PID: 5160 Comm: Xorg Tainted: GW 5.0.0-1 050-oem-osp1 #55-Ubuntu May 18 22:12:28 asgard kernel: [ 4906.887576] Hardware name: Dell Inc. XPS 13 9300/077Y9N, BIOS 1.0.7 02/26/2 020 May 18 22:12:28 asgard kernel: [ 4906.887604] RIP: 0010:hsw_wait_for_power_well_enable.isra.8+0x4c/0x50 [i915 ] May 18 22:12:28 asgard kernel: [ 4906.887607] Code: 01 c9 8b 70 04 6a 00 d3 e2 89 d1 e8 3e 86 04 00 85 c0 5a 75 02 c9 c3 48 c7 c6 98 42 5f c0 48 c7 c7 55 3d 5e c0 e8 a4 1c 9d df <0f> 0b c9 c3 0f 1f 44 00 00 55 ba 01 00 00 00 48 89 e5 41 57 41 56 May 18 22:12:28 asgard kernel: [ 4906.887609] RSP: 0018:add0048179c0 EFLAGS: 00010282 May 18 22:12:28 asgard kernel: [ 4906.887611] RAX: RBX: 9ce96e438000 RCX: 00 00 May 18 22:12:28 asgard kernel: [ 4906.887612] RDX: 006d RSI: a196492d RDI: 02 46 May 18 22:12:28 asgard kernel: [ 4906.887613] RBP: add0048179c0 R08: R09: a19648c0 May 18 22:12:28 asgard kernel: [ 4906.887614] R10: R11: 0001 R12: May 18 22:12:28 asgard kernel: [ 4906.887618] CS: 0010 DS: ES: CR0: 80050033 May 18 22:12:28 asgard kernel: [ 4906.887619] CR2: 55ea60d5b730 CR3: 00047a4a6006 CR4: 00760ee0 May 18 22:12:28 asgard kernel: [ 4906.887620] PKRU: 5554 May 18 22:12:28 asgard kernel: [ 4906.887621] Call Trace: May 18 22:12:28 asgard kernel: [ 4906.887650] hsw_power_well_enable+0xaf/0x1d0 [i915] May 18 22:12:28 asgard kernel: [ 4906.887678] icl_tc_phy_aux_power_well_enable+0x7f/0x90 [i915] May 18 22:12:28 asgard kernel: [ 4906.887704] intel_power_well_enable+0x3f/0x50 [i915] May 18 22:12:28 asgard kernel: [ 4906.887730] __intel_display_power_get_domain+0x75/0x90 [i915] May 18 22:12:28 asgard kernel: [ 4906.887758] intel_display_power_get+0x33/0x50 [i915] May 18 22:12:28 asgard kernel: [ 4906.887798] intel_dp_detect+0x96/0x5b0 [i915] May 18 22:12:28 asgard kernel: [ 4906.887802] ? ww_mutex_lock+0x64/0x70 May 18 22:12:28 asgard kernel: [ 4906.887811] drm_helper_probe_detect+0x50/0x90 [drm_kms_helper] May 18 22:12:28
[Touch-packages] [Bug 1857552] Re: [81NX, Realtek ALC285, Speaker, Internal] No sound at all
Hi all, I've freshly installed Ubuntu Mate 20.04 on LENOVO_MT_81NX_BU_idea_FM_Yoga S740-15IRH with the same problem. No sound no speakers. It seems the Realtek codec driver is not able to configure the speaker for the system. ** Attachment added: "dmesg output" https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1857552/+attachment/5373615/+files/bootmessages.txt -- 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/1857552 Title: [81NX, Realtek ALC285, Speaker, Internal] No sound at all Status in alsa-driver package in Ubuntu: Confirmed Bug description: In dual boot machine (lenove S740 laptop) sound is fine on windows side. Headphones work on linux side, but there is no sound at all from speakers on the ubuntu 19.10 ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10 Uname: Linux 5.3.0-24-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: hu-mka 1574 F pulseaudio hu-mka 5552 F alsamixer CurrentDesktop: ubuntu:GNOME Date: Wed Dec 25 20:14:17 2019 InstallationDate: Installed on 2019-12-22 (3 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: gdm1126 F pulseaudio hu-mka 1574 F pulseaudio hu-mka 5552 F alsamixer Symptom_Jack: Speaker, Internal Symptom_Type: No sound at all Title: [81NX, Realtek ALC285, Speaker, Internal] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/15/2019 dmi.bios.vendor: LENOVO dmi.bios.version: BKCN20WW(V1.02) dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0R32862 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 31 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo Yoga S740-15IRH dmi.modalias: dmi:bvnLENOVO:bvrBKCN20WW(V1.02):bd07/15/2019:svnLENOVO:pn81NX:pvrLenovoYogaS740-15IRH:rvnLENOVO:rnLNVNB161216:rvrSDK0R32862WIN:cvnLENOVO:ct31:cvrLenovoYogaS740-15IRH: dmi.product.family: Yoga S740-15IRH dmi.product.name: 81NX dmi.product.sku: LENOVO_MT_81NX_BU_idea_FM_Yoga S740-15IRH dmi.product.version: Lenovo Yoga S740-15IRH dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1857552/+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 1876629] Re: [HDA-Intel - HDA Intel PCH, playback] No sound output/recording at all
apport information ** Package changed: alsa-driver (Ubuntu) => linux (Ubuntu) ** Tags added: apport-collected ** Description changed: Updating the kernel from 4.15.0-91-generic to 4.15.0-99-generic caused all audio playback and recording to stop. Reverting to the old kernel corrects the problem. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.15.0-99.100-generic 4.15.18 Uname: Linux 4.15.0-99-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.14 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC0D0p: etzhaim1677 F...m pulseaudio /dev/snd/controlC0: etzhaim1677 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Sun May 3 23:59:43 2020 EcryptfsInUse: Yes InstallationDate: Installed on 2018-02-08 (815 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC0D0p: etzhaim1677 F...m pulseaudio /dev/snd/controlC0: gdm1245 F pulseaudio etzhaim1677 F pulseaudio Symptom_Type: No sound at all Title: [HDA-Intel - HDA Intel PCH, playback] No sound at all UpgradeStatus: Upgraded to bionic on 2018-05-08 (726 days ago) dmi.bios.date: 05/09/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.12.0 dmi.board.name: 09NT72 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.12.0:bd05/09/2019:svnDellInc.:pnInspiron5379:pvr:rvnDellInc.:rn09NT72:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: Inspiron dmi.product.name: Inspiron 5379 dmi.sys.vendor: Dell Inc. + --- + ProblemType: Bug + ApportVersion: 2.20.9-0ubuntu7.14 + Architecture: amd64 + AudioDevicesInUse: + USERPID ACCESS COMMAND + /dev/snd/controlC0: etzhaim1693 F pulseaudio + CurrentDesktop: ubuntu:GNOME + DistroRelease: Ubuntu 18.04 + EcryptfsInUse: Yes + HibernationDevice: RESUME=UUID=ecb7bced-50ae-4b4e-8a43-c89f47b1c956 + InstallationDate: Installed on 2018-02-08 (829 days ago) + InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1) + MachineType: Dell Inc. Inspiron 5379 + Package: linux (not installed) + ProcFB: 0 inteldrmfb + ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-99-generic root=UUID=92811e05-3a8b-47c4-b5e8-4283e1e2ec81 ro quiet splash i915.enable_psr=1 i915.disable_power_well=0 acpi_rev_override=5 pci=noaer pcie_aspm=force nmi_watchdog=0 vt.handoff=1 + ProcVersionSignature: Ubuntu 4.15.0-99.100-generic 4.15.18 + RelatedPackageVersions: + linux-restricted-modules-4.15.0-99-generic N/A + linux-backports-modules-4.15.0-99-generic N/A + linux-firmware 1.173.18 + Tags: bionic + Uname: Linux 4.15.0-99-generic x86_64 + UpgradeStatus: Upgraded to bionic on 2018-05-08 (741 days ago) + UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo + _MarkForUpload: True + dmi.bios.date: 05/09/2019 + dmi.bios.vendor: Dell Inc. + dmi.bios.version: 1.12.0 + dmi.board.name: 09NT72 + dmi.board.vendor: Dell Inc. + dmi.board.version: A00 + dmi.chassis.type: 10 + dmi.chassis.vendor: Dell Inc. + dmi.modalias: dmi:bvnDellInc.:bvr1.12.0:bd05/09/2019:svnDellInc.:pnInspiron5379:pvr:rvnDellInc.:rn09NT72:rvrA00:cvnDellInc.:ct10:cvr: + dmi.product.family: Inspiron + dmi.product.name: Inspiron 5379 + dmi.sys.vendor: Dell Inc. ** Attachment added: "AlsaInfo.txt" https://bugs.launchpad.net/bugs/1876629/+attachment/5373599/+files/AlsaInfo.txt -- 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/1876629 Title: [HDA-Intel - HDA Intel PCH, playback] No sound output/recording at all Status in linux package in Ubuntu: New Bug description: Updating the kernel from 4.15.0-91-generic to 4.15.0-99-generic caused all audio playback and recording to stop. Reverting to the old kernel corrects the problem. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.15.0-99.100-generic 4.15.18 Uname: Linux 4.15.0-99-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.14 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC0D0p: etzhaim1677 F...m pulseaudio /dev/snd/controlC0: etzhaim1677 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Sun May 3 23:59:43 2020 EcryptfsInUse: Yes InstallationDate: Installed on 2018-02-08 (815 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1) PackageArchitecture:
[Touch-packages] [Bug 1341256] Re: Press caps lock on bluetooth keyboard then the keyboard go death
I had the same problem. By pressing shift or caplock the MagicKeyboard wouldn't work anymore. It turns out that the problem comes from the fact that I use the keyboard on both ubuntu and windows (dual boot). When I connect the keyboard on ubuntu, it no longer works on windows because the keyboard and ubuntu share a sync key that windows does not know. When I associate the keyboard on windows, it still works on ubuntu (when it shouldn't) until I press caplocks. In fact, I think the bug is that the keyboard works a bit under ubuntu while the key is not good, if it returned an error we would find the problem right away. To solve the problem, I reassociated the keyboard with windows and then I copied the connection key and I copied it in the bluetooth configuration of ubuntu. Since my two OS share the same connection key for the keyboard, I don't have any more problems between the two OS and Capslock works well. I followed this tutorial : https://desktopi18n.wordpress.com/2018/02/02 /bluetooth-mouse-in-dual-boot-of-windows-10-and-linux/ Translated with www.DeepL.com/Translator (free version) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1341256 Title: Press caps lock on bluetooth keyboard then the keyboard go death Status in bluez package in Ubuntu: Confirmed Status in linux package in Ubuntu: Confirmed Bug description: I am typing using the Apple wireless keyboard,When I press 'caps lock',the keyboard don't work any more! So I go use keyboard on the Macbook.The key case have change,but the light on the key do not light on. I have to off the bluetooth then make it on again.Then reconnect the wireless keyboard. Yes,It work again. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: bluez 4.101-0ubuntu13 ProcVersionSignature: Ubuntu 3.16.0-3.8-generic 3.16.0-rc4 Uname: Linux 3.16.0-3-generic x86_64 NonfreeKernelModules: wl nvidia ApportVersion: 2.14.1-0ubuntu3.2 Architecture: amd64 CurrentDesktop: Unity Date: Sun Jul 13 17:12:23 2014 InstallationDate: Installed on 2014-03-08 (126 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Alpha amd64 (20140307) InterestingModules: bnep rfcomm btusb bluetooth MachineType: Apple Inc. MacBookPro9,1 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-3-generic.efi.signed root=UUID=6510f595-2f49-4798-953a-ed186346c60d ro irqpoll SourcePackage: bluez UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/08/2012 dmi.bios.vendor: Apple Inc. dmi.bios.version: MBP91.88Z.00D3.B08.1208081132 dmi.board.asset.tag: Base Board Asset Tag# dmi.board.name: Mac-4B7AC7E43945597E dmi.board.vendor: Apple Inc. dmi.board.version: MacBookPro9,1 dmi.chassis.type: 10 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-4B7AC7E43945597E dmi.modalias: dmi:bvnAppleInc.:bvrMBP91.88Z.00D3.B08.1208081132:bd08/08/2012:svnAppleInc.:pnMacBookPro9,1:pvr1.0:rvnAppleInc.:rnMac-4B7AC7E43945597E:rvrMacBookPro9,1:cvnAppleInc.:ct10:cvrMac-4B7AC7E43945597E: dmi.product.name: MacBookPro9,1 dmi.product.version: 1.0 dmi.sys.vendor: Apple Inc. hciconfig: hci0:Type: BR/EDR Bus: USB BD Address: 7C:D1:C3:79:A7:25 ACL MTU: 1021:8 SCO MTU: 64:1 UP RUNNING PSCAN RX bytes:119665 acl:5720 sco:0 events:2443 errors:0 TX bytes:13420 acl:640 sco:0 commands:718 errors:0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1341256/+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 1164016] Re: restore type-ahead find
Why can't you just move on? What is your stupid agenda? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-settings in Ubuntu. https://bugs.launchpad.net/bugs/1164016 Title: restore type-ahead find Status in Nautilus: Expired Status in nautilus package in Ubuntu: Fix Released Status in ubuntu-settings package in Ubuntu: Fix Released Bug description: GNOME removed type-ahead find in Nautilus 3.6, not without controversy: https://mail.gnome.org/archives/nautilus- list/2012-August/msg2.html Now when you type in a Nautilus window, Nautilus immediately performs a search in the current directory and all its subdirectories. I personally find this annoying. If I want to search, I'll click the search icon. Often I'm looking at a long directory listing and simply want to jump to a certain point in it, and type-ahead find works great for that. Would Ubuntu consider patching type-ahead find back in? To manage notifications about this bug go to: https://bugs.launchpad.net/nautilus/+bug/1164016/+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 1599159] Re: Yes/No/Cancel box that only says "text"
*** This bug is a duplicate of bug 1879150 *** https://bugs.launchpad.net/bugs/1879150 ** This bug has been marked a duplicate of bug 1879150 apport-kde shows 'text' instead of text in message box -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/1599159 Title: Yes/No/Cancel box that only says "text" Status in apport package in Ubuntu: New Bug description: I'm running Kubuntu 16.04. I ran 'apport-collect -p xorg 1584496' to help with reporting annother bug (https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1584496). After a few seconds of waiting while Apport was collecting information, a text box poped up. Its title was Apport, and its body only says "text". It gives me three optionsm, Yes, No, and Cancel. Atached is a screen shot of the window. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: apport-kde 2.20.1-0ubuntu2.1 ProcVersionSignature: Ubuntu 4.4.0-28.47-generic 4.4.13 Uname: Linux 4.4.0-28-generic x86_64 ApportLog: ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 CurrentDesktop: KDE Date: Tue Jul 5 08:21:29 2016 ExecutablePath: /usr/share/apport/apport-kde InstallationDate: Installed on 2016-06-16 (18 days ago) InstallationMedia: Kubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) InterpreterPath: /usr/bin/python2.7 PackageArchitecture: all SourcePackage: apport UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1599159/+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 1864689] Re: openssl in 20.04 can't connect to site that was fine in 19.10 and is fine in Chrome and Firefox
the openssl.cnf fix doesn't really work... allows me to connect to
sites, but when loading their pages, it takes forever. unusable. Also
tried SECLEVEL=0... same.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to openssl in Ubuntu.
https://bugs.launchpad.net/bugs/1864689
Title:
openssl in 20.04 can't connect to site that was fine in 19.10 and is
fine in Chrome and Firefox
Status in OpenSSL:
Unknown
Status in openssl package in Ubuntu:
Confirmed
Bug description:
openssl in Ubuntu 20.04 (focal) refuses to connect to a web site that
openssl in Ubuntu 19.10 (eoan), Chrome, and Firefox are all happy to
connect to.
Reproduce with: `curl -v https://www.toodledo.com/'
or: `openssl s_client -connect www.toodledo.com:443`
or: `python3 -c 'import requests;
requests.get("https://www.toodledo.com/;)'`
or: `wget https://www.toodledo.com/`
These worked in Ubuntu 19.10 and don't work in 20.04.
I've tried all sorts of things to debug this further and I've just run
into walls. I hope someone who understands more about this stuff will
be able to figure it out.
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: openssl 1.1.1d-2ubuntu3
ProcVersionSignature: Ubuntu 5.4.0-14.17-generic 5.4.18
Uname: Linux 5.4.0-14-generic x86_64
ApportVersion: 2.20.11-0ubuntu18
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Tue Feb 25 13:01:22 2020
InstallationDate: Installed on 2019-08-16 (192 days ago)
InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
SourcePackage: openssl
UpgradeStatus: Upgraded to focal on 2020-01-31 (25 days ago)
To manage notifications about this bug go to:
https://bugs.launchpad.net/openssl/+bug/1864689/+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 1850041] Re: Systemd-analyze blame returns "Bootup is not yet finished"
Seems to be fixed in Focal. ** Package changed: systemd (Ubuntu) => plymouth (Ubuntu) ** Changed in: plymouth (Ubuntu) Status: Confirmed => Fix Released -- 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/1850041 Title: Systemd-analyze blame returns "Bootup is not yet finished" Status in plymouth package in Ubuntu: Fix Released Bug description: Every time I run systemd-analyze blame, I get the message: Bootup is not yet finished (org.freedesktop.systemd1.Manager.FinishTimestampMonotonic=0). Please try again later. This, even if my laptop is on for several hours. Running systemctl list-jobs, returns: JOB UNIT TYPE STATE 1 graphical.target start waiting 95 systemd-update-utmp-runlevel.service start waiting 89 system-getty.slice start waiting 87 getty.target start waiting 21 setvtrgb.service start waiting 112 plymouth-quit-wait.service start running 88 getty@tty1.service start waiting 2 multi-user.targetstart waiting Boot time is about 90 seconds, before and after upgrading from 19.04 to 19.10. All applications start and run normally. My system is Ubuntu Budgie 19.10, working on a Dell Inspiron Laptop. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: systemd 242-7ubuntu3 ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1 Uname: Linux 5.3.0-19-generic x86_64 ApportVersion: 2.20.11-0ubuntu8 Architecture: amd64 CurrentDesktop: Budgie:GNOME Date: Sun Oct 27 09:54:26 2019 MachineType: Dell Inc. Inspiron 3421 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-19-generic root=UUID=2b7d5523-743f-465d-a24c-fadc4a3aa0f4 ro quiet splash vt.handoff=7 SourcePackage: systemd SystemdDelta: [EXTENDED] /lib/systemd/system/rc-local.service → /lib/systemd/system/rc-local.service.d/debian.conf [EXTENDED] /lib/systemd/system/systemd-timesyncd.service → /lib/systemd/system/systemd-timesyncd.service.d/disable-with-time-daemon.conf [EXTENDED] /lib/systemd/system/user@.service → /lib/systemd/system/user@.service.d/timeout.conf 3 overridden configuration files found. UpgradeStatus: Upgraded to eoan on 2019-10-23 (3 days ago) dmi.bios.date: 11/30/2012 dmi.bios.vendor: Dell Inc. dmi.bios.version: A02 dmi.board.vendor: Dell Inc. dmi.board.version: A02 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnDellInc.:bvrA02:bd11/30/2012:svnDellInc.:pnInspiron3421:pvrNotSpecified:rvnDellInc.:rn:rvrA02:cvnDellInc.:ct8:cvrNotSpecified: dmi.product.name: Inspiron 3421 dmi.product.sku: To be filled by O.E.M. dmi.product.version: Not Specified dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/plymouth/+bug/1850041/+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 1879150] Re: apport-kde shows 'text' instead of text in message box
** Also affects: apport (Ubuntu Eoan) Importance: Undecided Status: New ** Also affects: apport (Ubuntu Bionic) Importance: Undecided Status: New ** Also affects: apport (Ubuntu Xenial) Importance: Undecided Status: New ** Changed in: apport (Ubuntu Xenial) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/1879150 Title: apport-kde shows 'text' instead of text in message box Status in apport package in Ubuntu: In Progress Status in apport source package in Xenial: Confirmed Status in apport source package in Bionic: New Status in apport source package in Eoan: New Status in apport source package in Focal: Triaged Bug description: I had some other software crashing and wanting to report a bug, Apport displayed a pretty nonsensical message box (see the screenshot). $ lsb_release -rd Description:Ubuntu 20.04 LTS Release:20.04 $ apt-cache policy apport-kde apport-kde: Installed: 2.20.11-0ubuntu27 Candidate: 2.20.11-0ubuntu27 Version table: *** 2.20.11-0ubuntu27 500 500 http://de.archive.ubuntu.com/ubuntu focal/universe amd64 Packages 500 http://de.archive.ubuntu.com/ubuntu focal/universe i386 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: apport-kde 2.20.11-0ubuntu27 ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30 Uname: Linux 5.4.0-29-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: KDE Date: Sun May 17 14:11:30 2020 InstallationDate: Installed on 2015-12-11 (1618 days ago) InstallationMedia: Kubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805) PackageArchitecture: all SourcePackage: apport UpgradeStatus: Upgraded to focal on 2020-05-15 (1 days ago) mtime.conffile..etc.apport.crashdb.conf: 2019-11-21T10:33:51.640107 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1879150/+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 1861941] Re: bcache by-uuid links disappear after mounting bcache0
** Changed in: systemd (Ubuntu Groovy) Status: New => In Progress -- 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/1861941 Title: bcache by-uuid links disappear after mounting bcache0 Status in linux package in Ubuntu: Incomplete Status in linux-signed package in Ubuntu: New Status in systemd package in Ubuntu: In Progress Status in linux source package in Focal: New Status in linux-signed source package in Focal: New Status in systemd source package in Focal: New Status in linux source package in Groovy: Incomplete Status in linux-signed source package in Groovy: New Status in systemd source package in Groovy: In Progress Bug description: 1. root@ubuntu:~# lsb_release -rd Description: Ubuntu Focal Fossa (development branch) Release: 20.04 2. root@ubuntu:~# lsb_release -rd Description: Ubuntu Focal Fossa (development branch) Release: 20.04 root@ubuntu:~# apt-cache policy linux-image-virtual linux-image-virtual: Installed: 5.4.0.12.15 Candidate: 5.4.0.12.15 Version table: *** 5.4.0.12.15 500 500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages 100 /var/lib/dpkg/status root@ubuntu:~# apt-cache policy linux-image-5.4.0-12-generic linux-image-5.4.0-12-generic: Installed: 5.4.0-12.15 Candidate: 5.4.0-12.15 Version table: *** 5.4.0-12.15 500 500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages 100 /var/lib/dpkg/status 3. mount /dev/bcache0 && ls -al /dev/bcache/by-uuid/ + ls -al /dev/bcache/by-uuid/ total 0 drwxr-xr-x 2 root root 60 Feb 4 23:31 . drwxr-xr-x 3 root root 60 Feb 4 23:31 .. lrwxrwxrwx 1 root root 13 Feb 4 23:31 abdfd1f6-44ce-4266-91db-24667b9ae51a -> ../../bcache0 4. root@ubuntu:~# ls -al /dev/bcache/by-uuid ls: cannot access '/dev/bcache/by-uuid': No such file or directory ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-12-generic 5.4.0-12.15 ProcVersionSignature: Ubuntu 5.4.0-12.15-generic 5.4.8 Uname: Linux 5.4.0-12-generic x86_64 ApportVersion: 2.20.11-0ubuntu16 Architecture: amd64 Date: Tue Feb 4 23:31:52 2020 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=C.UTF-8 SHELL=/bin/bash SourcePackage: linux-signed-5.4 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1861941/+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 1879150] Re: apport-kde shows 'text' instead of text in message box
** Changed in: apport (Ubuntu Focal) Status: New => Triaged ** Changed in: apport (Ubuntu Focal) Importance: Undecided => Medium ** Changed in: apport (Ubuntu Focal) Milestone: None => ubuntu-20.04.1 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/1879150 Title: apport-kde shows 'text' instead of text in message box Status in apport package in Ubuntu: In Progress Status in apport source package in Xenial: Confirmed Status in apport source package in Bionic: New Status in apport source package in Eoan: New Status in apport source package in Focal: Triaged Bug description: I had some other software crashing and wanting to report a bug, Apport displayed a pretty nonsensical message box (see the screenshot). $ lsb_release -rd Description:Ubuntu 20.04 LTS Release:20.04 $ apt-cache policy apport-kde apport-kde: Installed: 2.20.11-0ubuntu27 Candidate: 2.20.11-0ubuntu27 Version table: *** 2.20.11-0ubuntu27 500 500 http://de.archive.ubuntu.com/ubuntu focal/universe amd64 Packages 500 http://de.archive.ubuntu.com/ubuntu focal/universe i386 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: apport-kde 2.20.11-0ubuntu27 ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30 Uname: Linux 5.4.0-29-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: KDE Date: Sun May 17 14:11:30 2020 InstallationDate: Installed on 2015-12-11 (1618 days ago) InstallationMedia: Kubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805) PackageArchitecture: all SourcePackage: apport UpgradeStatus: Upgraded to focal on 2020-05-15 (1 days ago) mtime.conffile..etc.apport.crashdb.conf: 2019-11-21T10:33:51.640107 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1879150/+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 1879150] Re: apport-kde shows 'text' instead of text in message box
** Branch linked: lp:~ubuntu-core-dev/ubuntu/groovy/apport/ubuntu -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/1879150 Title: apport-kde shows 'text' instead of text in message box Status in apport package in Ubuntu: In Progress Status in apport source package in Focal: Triaged Bug description: I had some other software crashing and wanting to report a bug, Apport displayed a pretty nonsensical message box (see the screenshot). $ lsb_release -rd Description:Ubuntu 20.04 LTS Release:20.04 $ apt-cache policy apport-kde apport-kde: Installed: 2.20.11-0ubuntu27 Candidate: 2.20.11-0ubuntu27 Version table: *** 2.20.11-0ubuntu27 500 500 http://de.archive.ubuntu.com/ubuntu focal/universe amd64 Packages 500 http://de.archive.ubuntu.com/ubuntu focal/universe i386 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: apport-kde 2.20.11-0ubuntu27 ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30 Uname: Linux 5.4.0-29-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: KDE Date: Sun May 17 14:11:30 2020 InstallationDate: Installed on 2015-12-11 (1618 days ago) InstallationMedia: Kubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805) PackageArchitecture: all SourcePackage: apport UpgradeStatus: Upgraded to focal on 2020-05-15 (1 days ago) mtime.conffile..etc.apport.crashdb.conf: 2019-11-21T10:33:51.640107 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1879150/+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 1879150] Re: apport-kde shows 'text' instead of text in message box
** Also affects: apport (Ubuntu Focal) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/1879150 Title: apport-kde shows 'text' instead of text in message box Status in apport package in Ubuntu: In Progress Status in apport source package in Focal: New Bug description: I had some other software crashing and wanting to report a bug, Apport displayed a pretty nonsensical message box (see the screenshot). $ lsb_release -rd Description:Ubuntu 20.04 LTS Release:20.04 $ apt-cache policy apport-kde apport-kde: Installed: 2.20.11-0ubuntu27 Candidate: 2.20.11-0ubuntu27 Version table: *** 2.20.11-0ubuntu27 500 500 http://de.archive.ubuntu.com/ubuntu focal/universe amd64 Packages 500 http://de.archive.ubuntu.com/ubuntu focal/universe i386 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: apport-kde 2.20.11-0ubuntu27 ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30 Uname: Linux 5.4.0-29-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: KDE Date: Sun May 17 14:11:30 2020 InstallationDate: Installed on 2015-12-11 (1618 days ago) InstallationMedia: Kubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805) PackageArchitecture: all SourcePackage: apport UpgradeStatus: Upgraded to focal on 2020-05-15 (1 days ago) mtime.conffile..etc.apport.crashdb.conf: 2019-11-21T10:33:51.640107 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1879150/+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 1164016] Re: restore type-ahead find
The real fix for whole modern GNOMEs Hell is simple - do not use it. Remove it (for example on 20.04 LTS with https://askubuntu.com/a/1233026/66509 ) and install normal DE instead - with Caja, Dolphin, Nemo, Thunar or whatever. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-settings in Ubuntu. https://bugs.launchpad.net/bugs/1164016 Title: restore type-ahead find Status in Nautilus: Expired Status in nautilus package in Ubuntu: Fix Released Status in ubuntu-settings package in Ubuntu: Fix Released Bug description: GNOME removed type-ahead find in Nautilus 3.6, not without controversy: https://mail.gnome.org/archives/nautilus- list/2012-August/msg2.html Now when you type in a Nautilus window, Nautilus immediately performs a search in the current directory and all its subdirectories. I personally find this annoying. If I want to search, I'll click the search icon. Often I'm looking at a long directory listing and simply want to jump to a certain point in it, and type-ahead find works great for that. Would Ubuntu consider patching type-ahead find back in? To manage notifications about this bug go to: https://bugs.launchpad.net/nautilus/+bug/1164016/+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 1878723] Re: Kernel panic when used with upstart after 0.11-4ubuntu2.1 update
@jfirebaugh: According to https://usn.ubuntu.com/4360-2/ The CVE fix is in the latest version. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to json-c in Ubuntu. https://bugs.launchpad.net/bugs/1878723 Title: Kernel panic when used with upstart after 0.11-4ubuntu2.1 update Status in json-c package in Ubuntu: Triaged Bug description: Installing the 0.11-4ubuntu2.1 security update on a Xenial system with upstart installed, the system crashes with a kernel panic. The error message is: [ 99.992278] Kernel panic - not syncing: Attempted to kill init! exitcode=0x0100 [ 99.992278] [ 99.996057] CPU: 0 PID: 1 Comm: init Not tainted 4.4.0-1105-aws #116-Ubuntu [ 99.996057] Hardware name: Xen HVM domU, BIOS 4.2.amazon 08/24/2006 [ 99.996057] 0086 0f10ff6977efbf32 88003d45fe10 8140926b [ 99.996057] 81caddf8 88003d45fea8 88003d45fe98 81195a84 [ 99.996057] 8810 88003d45fea8 88003d45fe40 0f10ff6977efbf32 [ 99.996057] Call Trace: [ 99.996057] [] dump_stack+0x6d/0x92 [ 99.996057] [] panic+0xd3/0x227 [ 99.996057] [] do_exit+0xb9d/0xba0 [ 99.996057] [] do_group_exit+0x47/0xb0 [ 99.996057] [] SyS_exit_group+0x14/0x20 [ 99.996057] [] entry_SYSCALL_64_fastpath+0x22/0xcb [ 99.996057] Kernel Offset: disabled Downgrading to libjson-c2_0.11-4ubuntu2 resolves the issue. Steps to reproduce: * Create a system with Xenial installed (I'm using an AWS instance with AMI ami-0f2ed58082cb08a4d) * Install upstart: apt-get install upstart-sysv * Reboot * Update apt and upgrade the packages: apt-get update && apt-get upgrade . This causes the kernel panic. * To repeat the kernel panic, run dpkg --configure -a To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/json-c/+bug/1878723/+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 1879150] Re: apport-kde shows 'text' instead of text in message box
** Changed in: apport (Ubuntu) Status: New => In Progress ** Changed in: apport (Ubuntu) Importance: Undecided => High ** Changed in: apport (Ubuntu) Assignee: (unassigned) => Brian Murray (brian-murray) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/1879150 Title: apport-kde shows 'text' instead of text in message box Status in apport package in Ubuntu: In Progress Bug description: I had some other software crashing and wanting to report a bug, Apport displayed a pretty nonsensical message box (see the screenshot). $ lsb_release -rd Description:Ubuntu 20.04 LTS Release:20.04 $ apt-cache policy apport-kde apport-kde: Installed: 2.20.11-0ubuntu27 Candidate: 2.20.11-0ubuntu27 Version table: *** 2.20.11-0ubuntu27 500 500 http://de.archive.ubuntu.com/ubuntu focal/universe amd64 Packages 500 http://de.archive.ubuntu.com/ubuntu focal/universe i386 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: apport-kde 2.20.11-0ubuntu27 ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30 Uname: Linux 5.4.0-29-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: KDE Date: Sun May 17 14:11:30 2020 InstallationDate: Installed on 2015-12-11 (1618 days ago) InstallationMedia: Kubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805) PackageArchitecture: all SourcePackage: apport UpgradeStatus: Upgraded to focal on 2020-05-15 (1 days ago) mtime.conffile..etc.apport.crashdb.conf: 2019-11-21T10:33:51.640107 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1879150/+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 1872863] Re: QEMU/KVM display is garbled when booting from kernel EFI stub due to missing bochs-drm module
This bug was fixed in the package kmod - 24-1ubuntu3.4 --- kmod (24-1ubuntu3.4) bionic; urgency=medium * Remove bochs-drm from d/modprobe.d/blacklist-framebuffer.conf to fix garbled screen with EFI based QEMU/KVM virtual machines which use VGA=std video devices. (LP: #1872863) -- Matthew Ruffell Thu, 09 Apr 2020 16:03:35 +1200 ** Changed in: kmod (Ubuntu Bionic) Status: Fix Committed => Fix Released -- 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/1872863 Title: QEMU/KVM display is garbled when booting from kernel EFI stub due to missing bochs-drm module Status in kmod package in Ubuntu: Fix Released Status in linux package in Ubuntu: Fix Released Status in kmod source package in Bionic: Fix Released Status in linux source package in Bionic: Fix Released Bug description: BugLink: https://bugs.launchpad.net/bugs/1872863 [Impact] A recent grub2 SRU, LP #1864533, now forces the kernel to boot via the kernel EFI stub whenever EFI is enabled. This causes problems for QEMU/KVM virtual machines which use the VGA=std video device, as the efifb driver yields an unreadable garbled screen. See the attached image. The correct framebuffer driver to use in this situation is bochs-drm, and modprobing it from a HWE kernel fixes the issues. bochs-drm is missing from Bionic since CONFIG_DRM_BOCHS was disabled in LP #1378648 due to bochs-drm causing problems in a PowerKVM machine. This problem appears to be fixed now, and bochs-drm has been re-enabled for Disco and up, in LP #1795857 and has been proven safe. This has also come up again in LP #1823152, as well as chatter on LP #1795857 to get this enabled on Bionic. The customer which is experiencing this issue cannot switch to VGA=qxl as a workaround, and must use VGA=std, hence I suggest we re-enable bochs-drm for Bionic. [Fix] I noticed on Focal, if you boot, the framebuffer is initially efifb: [ 0.603716] efifb: probing for efifb [ 0.603733] efifb: framebuffer at 0xc000, using 1876k, total 1875k [ 0.603735] efifb: mode is 800x600x32, linelength=3200, pages=1 [ 0.603736] efifb: scrolling: redraw [ 0.603738] efifb: Truecolor: size=8:8:8:8, shift=24:16:8:0 [ 0.604462] Console: switching to colour frame buffer device 100x37 [ 0.605829] fb0: EFI VGA frame buffer device This soon changes to bochs-drm about a second later: [ 0.935988] bochs-drm :00:01.0: remove_conflicting_pci_framebuffers: bar 0: 0xc000 -> 0xc0ff [ 0.937023] bochs-drm :00:01.0: remove_conflicting_pci_framebuffers: bar 2: 0xc1c8c000 -> 0xc1c8cfff [ 0.937776] checking generic (c000 1d5000) vs hw (c000 100) [ 0.937776] fb0: switching to bochsdrmfb from EFI VGA [ 0.939085] Console: switching to colour dummy device 80x25 [ 0.939117] bochs-drm :00:01.0: vgaarb: deactivate vga console [ 0.939210] [drm] Found bochs VGA, ID 0xb0c5. [ 0.939212] [drm] Framebuffer size 16384 kB @ 0xc000, mmio @ 0xc1c8c000. [ 0.941955] lpc_ich :00:1f.0: I/O space for GPIO uninitialized [ 0.942069] [TTM] Zone kernel: Available graphics memory: 2006780 KiB [ 0.942081] [TTM] Initializing pool allocator [ 0.942089] [TTM] Initializing DMA pool allocator [ 0.943026] virtio_blk virtio2: [vda] 20971520 512-byte logical blocks (10.7 GB/10.0 GiB) [ 0.944019] [drm] Found EDID data blob. [ 0.944162] [drm] Initialized bochs-drm 1.0.0 20130925 for :00:01.0 on minor 0 [ 0.944979] fbcon: bochs-drmdrmfb (fb0) is primary device [ 0.947712] Console: switching to colour frame buffer device 128x48 On bionic, the framebuffer never changes from efifb, since the bochs- drm kernel module is not built, and it is also present on the module banlist in /etc/modprobe.d/blacklist-framebuffer.conf bochs-drm needs to be enabled to be built in the kernel config, and removed from the module blacklist in kmod. [Testcase] Create a new QEMU/KVM virtual machine, I used virt-manager. Before you install the OS, check the box to modify settings before install. In the "Overview" tab, enable EFI by setting the firmware to "UEFI x86_64: /usr/share/OVMF/OVMF_CODE.secboot.fd". Set the video device to qxl while you install Bionic. Once the install is done, reboot, do a "apt update" and "apt upgrade", to ensure you have grub2 2.02-2ubuntu8.15 installed. Shut the VM down, and set the video device to VGA. Or VGA=std if you use the QEMU command line. Start the VM up, and the screen will be garbled. See attached picture. If you install my test packages, which are available here: https://launchpad.net/~mruffell/+archive/ubuntu/sf272653-test Instructions to install (on a bionic system): 1) Enable bionic-proposed 2) sudo apt-get update 3) sudo apt install linux-image-unsigned-4.15.0-96-generic
[Touch-packages] [Bug 1877023] Re: Unhandled exception in check_ignored()
** Changed in: apport (Ubuntu)
Importance: Undecided => Medium
** Changed in: apport (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apport in Ubuntu.
https://bugs.launchpad.net/bugs/1877023
Title:
Unhandled exception in check_ignored()
Status in apport package in Ubuntu:
Confirmed
Bug description:
Hi,
I have found a security issue on apport 2.20.11 and earlier.
## Vulnerability
apport 2.20.11 and earlier have an unhandled exception vulnerability during
parsing apport-ignore.xml.
An attacker can cause a denial of service (i.e., application crash) via a
crafted apport-ignore.xml file.
## Description
Reports can be suppressed by blacklisting in apport-ignore.xml.
This is an example of apport-ignore.xml
Unfortunately, it may cause an unhandled exception when 'mtime'
attribute is specified as a string value, not a number like this.
It may disrupt apport service and allow an attacker to potentially
enable a denial of service via local access.
The flaw lies in improper exception handling of 'mtime' attribute in
apport-ignore.xml (see
https://git.launchpad.net/ubuntu/+source/apport/tree/apport/report.py?h=applied/ubuntu/devel#n1104).
## Log
Here is /var/log/apport.log when the above exception occurs.
ERROR: apport (pid 25904) Tue May 5 18:38:21 2020: Unhandled exception:
Traceback (most recent call last):
File "/usr/share/apport/apport", line 629, in
if info.check_ignored():
File "/usr/lib/python3/dist-packages/apport/report.py", line 1082, in
check_ignored
if float(ignore.getAttribute('mtime')) >= cur_mtime:
ValueError: could not convert string to float: 'string'
Sincerely,
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1877023/+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 1872863] Update Released
The verification of the Stable Release Update for kmod has completed successfully and the package is now being released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- 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/1872863 Title: QEMU/KVM display is garbled when booting from kernel EFI stub due to missing bochs-drm module Status in kmod package in Ubuntu: Fix Released Status in linux package in Ubuntu: Fix Released Status in kmod source package in Bionic: Fix Committed Status in linux source package in Bionic: Fix Released Bug description: BugLink: https://bugs.launchpad.net/bugs/1872863 [Impact] A recent grub2 SRU, LP #1864533, now forces the kernel to boot via the kernel EFI stub whenever EFI is enabled. This causes problems for QEMU/KVM virtual machines which use the VGA=std video device, as the efifb driver yields an unreadable garbled screen. See the attached image. The correct framebuffer driver to use in this situation is bochs-drm, and modprobing it from a HWE kernel fixes the issues. bochs-drm is missing from Bionic since CONFIG_DRM_BOCHS was disabled in LP #1378648 due to bochs-drm causing problems in a PowerKVM machine. This problem appears to be fixed now, and bochs-drm has been re-enabled for Disco and up, in LP #1795857 and has been proven safe. This has also come up again in LP #1823152, as well as chatter on LP #1795857 to get this enabled on Bionic. The customer which is experiencing this issue cannot switch to VGA=qxl as a workaround, and must use VGA=std, hence I suggest we re-enable bochs-drm for Bionic. [Fix] I noticed on Focal, if you boot, the framebuffer is initially efifb: [ 0.603716] efifb: probing for efifb [ 0.603733] efifb: framebuffer at 0xc000, using 1876k, total 1875k [ 0.603735] efifb: mode is 800x600x32, linelength=3200, pages=1 [ 0.603736] efifb: scrolling: redraw [ 0.603738] efifb: Truecolor: size=8:8:8:8, shift=24:16:8:0 [ 0.604462] Console: switching to colour frame buffer device 100x37 [ 0.605829] fb0: EFI VGA frame buffer device This soon changes to bochs-drm about a second later: [ 0.935988] bochs-drm :00:01.0: remove_conflicting_pci_framebuffers: bar 0: 0xc000 -> 0xc0ff [ 0.937023] bochs-drm :00:01.0: remove_conflicting_pci_framebuffers: bar 2: 0xc1c8c000 -> 0xc1c8cfff [ 0.937776] checking generic (c000 1d5000) vs hw (c000 100) [ 0.937776] fb0: switching to bochsdrmfb from EFI VGA [ 0.939085] Console: switching to colour dummy device 80x25 [ 0.939117] bochs-drm :00:01.0: vgaarb: deactivate vga console [ 0.939210] [drm] Found bochs VGA, ID 0xb0c5. [ 0.939212] [drm] Framebuffer size 16384 kB @ 0xc000, mmio @ 0xc1c8c000. [ 0.941955] lpc_ich :00:1f.0: I/O space for GPIO uninitialized [ 0.942069] [TTM] Zone kernel: Available graphics memory: 2006780 KiB [ 0.942081] [TTM] Initializing pool allocator [ 0.942089] [TTM] Initializing DMA pool allocator [ 0.943026] virtio_blk virtio2: [vda] 20971520 512-byte logical blocks (10.7 GB/10.0 GiB) [ 0.944019] [drm] Found EDID data blob. [ 0.944162] [drm] Initialized bochs-drm 1.0.0 20130925 for :00:01.0 on minor 0 [ 0.944979] fbcon: bochs-drmdrmfb (fb0) is primary device [ 0.947712] Console: switching to colour frame buffer device 128x48 On bionic, the framebuffer never changes from efifb, since the bochs- drm kernel module is not built, and it is also present on the module banlist in /etc/modprobe.d/blacklist-framebuffer.conf bochs-drm needs to be enabled to be built in the kernel config, and removed from the module blacklist in kmod. [Testcase] Create a new QEMU/KVM virtual machine, I used virt-manager. Before you install the OS, check the box to modify settings before install. In the "Overview" tab, enable EFI by setting the firmware to "UEFI x86_64: /usr/share/OVMF/OVMF_CODE.secboot.fd". Set the video device to qxl while you install Bionic. Once the install is done, reboot, do a "apt update" and "apt upgrade", to ensure you have grub2 2.02-2ubuntu8.15 installed. Shut the VM down, and set the video device to VGA. Or VGA=std if you use the QEMU command line. Start the VM up, and the screen will be garbled. See attached picture. If you install my test packages, which are available here: https://launchpad.net/~mruffell/+archive/ubuntu/sf272653-test Instructions to install (on a bionic system): 1) Enable bionic-proposed 2) sudo apt-get update 3) sudo apt install linux-image-unsigned-4.15.0-96-generic
Re: [Touch-packages] [Bug 1877895] Re: package udev 245.4-4ubuntu3 failed to install/upgrade: o subprocesso instalado, do pacote udev, o script post-installation retornou erro do status de saída 1
I will update, if there is a problem I report, ok. thanks for you help Em segunda-feira, 18 de maio de 2020 09:55:54 BRT, Balint Reczey escreveu: I can't download the attachment, but it looks quite odd already from the original name. Please try reinstalling udev. -- You received this bug notification because you are subscribed to the bug report. https://bugs.launchpad.net/bugs/1877895 Title: package udev 245.4-4ubuntu3 failed to install/upgrade: o subprocesso instalado, do pacote udev, o script post-installation retornou erro do status de saída 1 Status in systemd package in Ubuntu: Incomplete Bug description: after updating from 18.04 to 20.04, appears errors constantly ProblemType: Package DistroRelease: Ubuntu 20.04 Package: udev 245.4-4ubuntu3 ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30 Uname: Linux 5.4.0-29-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CustomUdevRuleFiles: 70-snap.spotify.rules 70-snap.core.rules Date: Sat May 9 10:24:26 2020 ErrorMessage: o subprocesso instalado, do pacote udev, o script post-installation retornou erro do status de saída 1 InstallationDate: Installed on 2020-05-09 (1 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) MachineType: Sony Corporation SVE15125CBW ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-29-generic root=UUID=53223737-2091-4487-a0b3-a2b80db164ad ro quiet splash Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: /usr/bin/python2.7, Python 2.7.18rc1, python-minimal, 2.7.15~rc1-1 RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.2 SourcePackage: systemd Title: package udev 245.4-4ubuntu3 failed to install/upgrade: o subprocesso instalado, do pacote udev, o script post-installation retornou erro do status de saída 1 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/14/2012 dmi.bios.vendor: Insyde Corp. dmi.bios.version: R0170D5 dmi.board.asset.tag: N/A dmi.board.name: VAIO dmi.board.vendor: Sony Corporation dmi.board.version: N/A dmi.chassis.asset.tag: N/A dmi.chassis.type: 10 dmi.chassis.vendor: Sony Corporation dmi.chassis.version: N/A dmi.modalias: dmi:bvnInsydeCorp.:bvrR0170D5:bd11/14/2012:svnSonyCorporation:pnSVE15125CBW:pvrC800EQPLK:rvnSonyCorporation:rnVAIO:rvrN/A:cvnSonyCorporation:ct10:cvrN/A: dmi.product.family: VAIO dmi.product.name: SVE15125CBW dmi.product.sku: 54508549 dmi.product.version: C800EQPLK dmi.sys.vendor: Sony Corporation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1877895/+subscriptions -- 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/1877895 Title: package udev 245.4-4ubuntu3 failed to install/upgrade: o subprocesso instalado, do pacote udev, o script post-installation retornou erro do status de saída 1 Status in systemd package in Ubuntu: Incomplete Bug description: after updating from 18.04 to 20.04, appears errors constantly ProblemType: Package DistroRelease: Ubuntu 20.04 Package: udev 245.4-4ubuntu3 ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30 Uname: Linux 5.4.0-29-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CustomUdevRuleFiles: 70-snap.spotify.rules 70-snap.core.rules Date: Sat May 9 10:24:26 2020 ErrorMessage: o subprocesso instalado, do pacote udev, o script post-installation retornou erro do status de saída 1 InstallationDate: Installed on 2020-05-09 (1 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) MachineType: Sony Corporation SVE15125CBW ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-29-generic root=UUID=53223737-2091-4487-a0b3-a2b80db164ad ro quiet splash Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: /usr/bin/python2.7, Python 2.7.18rc1, python-minimal, 2.7.15~rc1-1 RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.2 SourcePackage: systemd Title: package udev 245.4-4ubuntu3 failed to install/upgrade: o subprocesso instalado, do pacote udev, o script post-installation retornou erro do status de saída 1 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/14/2012 dmi.bios.vendor: Insyde Corp. dmi.bios.version: R0170D5 dmi.board.asset.tag: N/A dmi.board.name: VAIO dmi.board.vendor: Sony Corporation dmi.board.version: N/A dmi.chassis.asset.tag: N/A dmi.chassis.type: 10 dmi.chassis.vendor: Sony Corporation dmi.chassis.version: N/A dmi.modalias:
[Touch-packages] [Bug 1164016] Re: restore type-ahead find
For reference only: Old gnome bug resolved as obsolete: https://bugzilla.gnome.org/show_bug.cgi?id=681871 Recent bugs opened with same topic: https://gitlab.gnome.org/GNOME/nautilus/-/issues/1157 - with 9 related tickets closed https://gitlab.gnome.org/GNOME/nautilus/-/issues/1154 ** Bug watch added: bugzilla.gnome.org/ #681871 https://bugzilla.gnome.org/show_bug.cgi?id=681871 ** Bug watch added: gitlab.gnome.org/GNOME/nautilus/-/issues #1157 https://gitlab.gnome.org/GNOME/nautilus/-/issues/1157 ** Bug watch added: gitlab.gnome.org/GNOME/nautilus/-/issues #1154 https://gitlab.gnome.org/GNOME/nautilus/-/issues/1154 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-settings in Ubuntu. https://bugs.launchpad.net/bugs/1164016 Title: restore type-ahead find Status in Nautilus: Expired Status in nautilus package in Ubuntu: Fix Released Status in ubuntu-settings package in Ubuntu: Fix Released Bug description: GNOME removed type-ahead find in Nautilus 3.6, not without controversy: https://mail.gnome.org/archives/nautilus- list/2012-August/msg2.html Now when you type in a Nautilus window, Nautilus immediately performs a search in the current directory and all its subdirectories. I personally find this annoying. If I want to search, I'll click the search icon. Often I'm looking at a long directory listing and simply want to jump to a certain point in it, and type-ahead find works great for that. Would Ubuntu consider patching type-ahead find back in? To manage notifications about this bug go to: https://bugs.launchpad.net/nautilus/+bug/1164016/+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 1864689] Re: openssl in 20.04 can't connect to site that was fine in 19.10 and is fine in Chrome and Firefox
Also affects me with many HTTPS sites, such as teams.microsoft.com, but
haven't been able to post a bug here because SSL or whatever isn't
working. I imagine many can't post that it's broken, but tons of
websites aren't working in Firefox or chrome or wget for me.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to openssl in Ubuntu.
https://bugs.launchpad.net/bugs/1864689
Title:
openssl in 20.04 can't connect to site that was fine in 19.10 and is
fine in Chrome and Firefox
Status in OpenSSL:
Unknown
Status in openssl package in Ubuntu:
Confirmed
Bug description:
openssl in Ubuntu 20.04 (focal) refuses to connect to a web site that
openssl in Ubuntu 19.10 (eoan), Chrome, and Firefox are all happy to
connect to.
Reproduce with: `curl -v https://www.toodledo.com/'
or: `openssl s_client -connect www.toodledo.com:443`
or: `python3 -c 'import requests;
requests.get("https://www.toodledo.com/;)'`
or: `wget https://www.toodledo.com/`
These worked in Ubuntu 19.10 and don't work in 20.04.
I've tried all sorts of things to debug this further and I've just run
into walls. I hope someone who understands more about this stuff will
be able to figure it out.
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: openssl 1.1.1d-2ubuntu3
ProcVersionSignature: Ubuntu 5.4.0-14.17-generic 5.4.18
Uname: Linux 5.4.0-14-generic x86_64
ApportVersion: 2.20.11-0ubuntu18
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Tue Feb 25 13:01:22 2020
InstallationDate: Installed on 2019-08-16 (192 days ago)
InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
SourcePackage: openssl
UpgradeStatus: Upgraded to focal on 2020-01-31 (25 days ago)
To manage notifications about this bug go to:
https://bugs.launchpad.net/openssl/+bug/1864689/+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 1878723] Re: Kernel panic when used with upstart after 0.11-4ubuntu2.1 update
@cnewcomer, can you clarify whether or not 0.11-4ubuntu2.5 contains the (fixed) security update? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to json-c in Ubuntu. https://bugs.launchpad.net/bugs/1878723 Title: Kernel panic when used with upstart after 0.11-4ubuntu2.1 update Status in json-c package in Ubuntu: Triaged Bug description: Installing the 0.11-4ubuntu2.1 security update on a Xenial system with upstart installed, the system crashes with a kernel panic. The error message is: [ 99.992278] Kernel panic - not syncing: Attempted to kill init! exitcode=0x0100 [ 99.992278] [ 99.996057] CPU: 0 PID: 1 Comm: init Not tainted 4.4.0-1105-aws #116-Ubuntu [ 99.996057] Hardware name: Xen HVM domU, BIOS 4.2.amazon 08/24/2006 [ 99.996057] 0086 0f10ff6977efbf32 88003d45fe10 8140926b [ 99.996057] 81caddf8 88003d45fea8 88003d45fe98 81195a84 [ 99.996057] 8810 88003d45fea8 88003d45fe40 0f10ff6977efbf32 [ 99.996057] Call Trace: [ 99.996057] [] dump_stack+0x6d/0x92 [ 99.996057] [] panic+0xd3/0x227 [ 99.996057] [] do_exit+0xb9d/0xba0 [ 99.996057] [] do_group_exit+0x47/0xb0 [ 99.996057] [] SyS_exit_group+0x14/0x20 [ 99.996057] [] entry_SYSCALL_64_fastpath+0x22/0xcb [ 99.996057] Kernel Offset: disabled Downgrading to libjson-c2_0.11-4ubuntu2 resolves the issue. Steps to reproduce: * Create a system with Xenial installed (I'm using an AWS instance with AMI ami-0f2ed58082cb08a4d) * Install upstart: apt-get install upstart-sysv * Reboot * Update apt and upgrade the packages: apt-get update && apt-get upgrade . This causes the kernel panic. * To repeat the kernel panic, run dpkg --configure -a To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/json-c/+bug/1878723/+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 1875910] Re: Command to update mirror list
** Changed in: launchpad Status: New => Triaged ** Changed in: launchpad Importance: Undecided => Medium -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to python-apt in Ubuntu. https://bugs.launchpad.net/bugs/1875910 Title: Command to update mirror list Status in Launchpad itself: Triaged Status in python-apt package in Ubuntu: Triaged Bug description: I see a lot of issues regarding outdated Ubuntu.mirrors file, I think there should be a command that imports the list of mirrors from https://launchpad.net/ubuntu/+archivemirrors and updates the templates/Ubuntu.mirrors file, then in the UI add a button that can update the list of Mirrors. I don't see the point of needing a new release every time the list needs to be updated. I want a mirror that was updated yesterday, because is the closest to my location, but it is not in the list, and as you can see there are lots of issues from people that could have been avoided with this. This is not really a bug, but a feature. Also could be great if there was some kind of filter, like if you select now in Ubuntu 19.10 a ftp mirror and update it will fail, and the UI gets broken (you can't even close the window, you have to kill it), so doing this update should just import those mirrors that are safe to use. To manage notifications about this bug go to: https://bugs.launchpad.net/launchpad/+bug/1875910/+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 1164016] Re: restore type-ahead find
Actually this one is marked as fixed because it was indeed fixed several years ago, but then the fix was lost (i.e. the patch not rewritten) when a new version of gnome was released, "because" search is faster now, which according to some nonsensical reasoning by those who don't uderstand this issue, meant to them that the issue was no longer relevant. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-settings in Ubuntu. https://bugs.launchpad.net/bugs/1164016 Title: restore type-ahead find Status in Nautilus: Expired Status in nautilus package in Ubuntu: Fix Released Status in ubuntu-settings package in Ubuntu: Fix Released Bug description: GNOME removed type-ahead find in Nautilus 3.6, not without controversy: https://mail.gnome.org/archives/nautilus- list/2012-August/msg2.html Now when you type in a Nautilus window, Nautilus immediately performs a search in the current directory and all its subdirectories. I personally find this annoying. If I want to search, I'll click the search icon. Often I'm looking at a long directory listing and simply want to jump to a certain point in it, and type-ahead find works great for that. Would Ubuntu consider patching type-ahead find back in? To manage notifications about this bug go to: https://bugs.launchpad.net/nautilus/+bug/1164016/+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 1164016] Re: restore type-ahead find
This ticket was opened 7 years ago, and after 160 comments, nobody seems to care about. I lost all my hope that ubuntu or gnome are going to take care of this, probably 259 affected people is too little for them. I installed nemo 1 year ago, and didn't come back, I'm happy with nemo bringing me back the F3 shortcut to navigate two trees simultaneously, and the type-ahead behaving as expected, and at the same time being able to search with Ctrl-F. Sad answer to community, but reading the history of gnome project it seems is not uncommon. I see gnome resolved the related ticket as obsolete - so, probably would be better to do the same with this ticket here at ubuntu - and let people move ahead (to nemo) without false hope :-) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-settings in Ubuntu. https://bugs.launchpad.net/bugs/1164016 Title: restore type-ahead find Status in Nautilus: Expired Status in nautilus package in Ubuntu: Fix Released Status in ubuntu-settings package in Ubuntu: Fix Released Bug description: GNOME removed type-ahead find in Nautilus 3.6, not without controversy: https://mail.gnome.org/archives/nautilus- list/2012-August/msg2.html Now when you type in a Nautilus window, Nautilus immediately performs a search in the current directory and all its subdirectories. I personally find this annoying. If I want to search, I'll click the search icon. Often I'm looking at a long directory listing and simply want to jump to a certain point in it, and type-ahead find works great for that. Would Ubuntu consider patching type-ahead find back in? To manage notifications about this bug go to: https://bugs.launchpad.net/nautilus/+bug/1164016/+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 1864689] Re: openssl in 20.04 can't connect to site that was fine in 19.10 and is fine in Chrome and Firefox
This bug affects me too, with a client certificate that now "magically"
does not match the requirements.
Ironically, the error message says only:
OpenSSL error error:140AB18E:SSL routines:SSL_CTX_use_certificate:ca md
too weak, (no key found, wrong pass phrase, or wrong file format?)
although there was no MD5 signature involved at all. So, even when you
know that with OpenSSL 1.1, an "SSL security level" has been introduced,
and that Ubuntu has set that level to 2, it is hard to find that it
deprecates SHA1 now (see
https://www.openssl.org/docs/manmaster/man3/SSL_CTX_set_security_level.html).
Thus, even for more knowledgable people than me this is a major hassle
to find and/or fix. I wonder why Ubuntu has chosen to raise the level
that high considering that the documentation page contains a clear
warning indication:
"WARNING at this time setting the security level higher than 1 for
general internet use is likely to cause considerable interoperability
issues and is not recommended. This is because the SHA1 algorithm is
very widely used in certificates and will be rejected at levels higher
than 1 because it only offers 80 bits of security."
I think that this is an extremely unwise choice for an OS to make.
That being said, here is the fix (also hard to find):
In /etc/ssl/openssl.cnf, add this line before the start of the file:
openssl_conf = default_conf
At the end of the file, add these lines:
[default_conf]
ssl_conf = ssl_sect
[ssl_sect]
system_default = system_default_sect
[system_default_sect]
CipherString = DEFAULT:@SECLEVEL=1
This will bring down the SSL security level to the former level of 1.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to openssl in Ubuntu.
https://bugs.launchpad.net/bugs/1864689
Title:
openssl in 20.04 can't connect to site that was fine in 19.10 and is
fine in Chrome and Firefox
Status in OpenSSL:
Unknown
Status in openssl package in Ubuntu:
Confirmed
Bug description:
openssl in Ubuntu 20.04 (focal) refuses to connect to a web site that
openssl in Ubuntu 19.10 (eoan), Chrome, and Firefox are all happy to
connect to.
Reproduce with: `curl -v https://www.toodledo.com/'
or: `openssl s_client -connect www.toodledo.com:443`
or: `python3 -c 'import requests;
requests.get("https://www.toodledo.com/;)'`
or: `wget https://www.toodledo.com/`
These worked in Ubuntu 19.10 and don't work in 20.04.
I've tried all sorts of things to debug this further and I've just run
into walls. I hope someone who understands more about this stuff will
be able to figure it out.
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: openssl 1.1.1d-2ubuntu3
ProcVersionSignature: Ubuntu 5.4.0-14.17-generic 5.4.18
Uname: Linux 5.4.0-14-generic x86_64
ApportVersion: 2.20.11-0ubuntu18
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Tue Feb 25 13:01:22 2020
InstallationDate: Installed on 2019-08-16 (192 days ago)
InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
SourcePackage: openssl
UpgradeStatus: Upgraded to focal on 2020-01-31 (25 days ago)
To manage notifications about this bug go to:
https://bugs.launchpad.net/openssl/+bug/1864689/+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
Re: [Touch-packages] [Bug 1877895] Re: package udev 245.4-4ubuntu3 failed to install/upgrade: o subprocesso instalado, do pacote udev, o script post-installation retornou erro do status de saída 1
hello, follows attached Em segunda-feira, 18 de maio de 2020 07:45:57 BRT, Balint Reczey escreveu: Please attach output of: cat /lib/systemd/system/systemd-udevd.service Running the following command may fix the issue: sudo apt install --reinstall udev ** Changed in: systemd (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are subscribed to the bug report. https://bugs.launchpad.net/bugs/1877895 Title: package udev 245.4-4ubuntu3 failed to install/upgrade: o subprocesso instalado, do pacote udev, o script post-installation retornou erro do status de saída 1 Status in systemd package in Ubuntu: Incomplete Bug description: after updating from 18.04 to 20.04, appears errors constantly ProblemType: Package DistroRelease: Ubuntu 20.04 Package: udev 245.4-4ubuntu3 ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30 Uname: Linux 5.4.0-29-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CustomUdevRuleFiles: 70-snap.spotify.rules 70-snap.core.rules Date: Sat May 9 10:24:26 2020 ErrorMessage: o subprocesso instalado, do pacote udev, o script post-installation retornou erro do status de saída 1 InstallationDate: Installed on 2020-05-09 (1 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) MachineType: Sony Corporation SVE15125CBW ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-29-generic root=UUID=53223737-2091-4487-a0b3-a2b80db164ad ro quiet splash Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: /usr/bin/python2.7, Python 2.7.18rc1, python-minimal, 2.7.15~rc1-1 RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.2 SourcePackage: systemd Title: package udev 245.4-4ubuntu3 failed to install/upgrade: o subprocesso instalado, do pacote udev, o script post-installation retornou erro do status de saída 1 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/14/2012 dmi.bios.vendor: Insyde Corp. dmi.bios.version: R0170D5 dmi.board.asset.tag: N/A dmi.board.name: VAIO dmi.board.vendor: Sony Corporation dmi.board.version: N/A dmi.chassis.asset.tag: N/A dmi.chassis.type: 10 dmi.chassis.vendor: Sony Corporation dmi.chassis.version: N/A dmi.modalias: dmi:bvnInsydeCorp.:bvrR0170D5:bd11/14/2012:svnSonyCorporation:pnSVE15125CBW:pvrC800EQPLK:rvnSonyCorporation:rnVAIO:rvrN/A:cvnSonyCorporation:ct10:cvrN/A: dmi.product.family: VAIO dmi.product.name: SVE15125CBW dmi.product.sku: 54508549 dmi.product.version: C800EQPLK dmi.sys.vendor: Sony Corporation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1877895/+subscriptions ** Attachment added: "=?UTF-8?b?Y2F0?=" https://bugs.launchpad.net/bugs/1877895/+attachment/5373384/+files/%3D%3FUTF-8%3Fb%3FY2F0%3F%3D -- 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/1877895 Title: package udev 245.4-4ubuntu3 failed to install/upgrade: o subprocesso instalado, do pacote udev, o script post-installation retornou erro do status de saída 1 Status in systemd package in Ubuntu: Incomplete Bug description: after updating from 18.04 to 20.04, appears errors constantly ProblemType: Package DistroRelease: Ubuntu 20.04 Package: udev 245.4-4ubuntu3 ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30 Uname: Linux 5.4.0-29-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CustomUdevRuleFiles: 70-snap.spotify.rules 70-snap.core.rules Date: Sat May 9 10:24:26 2020 ErrorMessage: o subprocesso instalado, do pacote udev, o script post-installation retornou erro do status de saída 1 InstallationDate: Installed on 2020-05-09 (1 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) MachineType: Sony Corporation SVE15125CBW ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-29-generic root=UUID=53223737-2091-4487-a0b3-a2b80db164ad ro quiet splash Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: /usr/bin/python2.7, Python 2.7.18rc1, python-minimal, 2.7.15~rc1-1 RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.2 SourcePackage: systemd Title: package udev 245.4-4ubuntu3 failed to install/upgrade: o subprocesso instalado, do pacote udev, o script post-installation retornou erro do status de saída 1 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/14/2012 dmi.bios.vendor: Insyde Corp. dmi.bios.version: R0170D5 dmi.board.asset.tag: N/A dmi.board.name: VAIO dmi.board.vendor: Sony Corporation dmi.board.version: N/A dmi.chassis.asset.tag: N/A dmi.chassis.type: 10 dmi.chassis.vendor:
[Touch-packages] [Bug 1879182] Re: Sound cuts off and back on randomly during online streaming of videos
journalctl -b 0 log attached The sound goes out with a double pop sound and comes back on within 10 minutes with a double pop sound. During the time when the sound is off, crackling noises can be heard in sync with the audio that is playing. ** Attachment added: "journal_log.txt" https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1879182/+attachment/5373493/+files/journal_log.txt -- 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/1879182 Title: Sound cuts off and back on randomly during online streaming of videos Status in pulseaudio package in Ubuntu: Incomplete Bug description: Sound shuts off and turns back on again with two pop clicks. When the sound is off, if i turn up the volume to the max, i can hear crackling sound in speakers in tune with sound playing on the computer. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: pulseaudio 1:13.99.1-1ubuntu3.2 ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30 Uname: Linux 5.4.0-29-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: siddahuja 31829 F pulseaudio /dev/snd/controlC0: siddahuja 31829 F pulseaudio /dev/snd/pcmC0D0p: siddahuja 31829 F...m pulseaudio /dev/snd/timer: siddahuja 31829 f pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sun May 17 23:56:27 2020 InstallationDate: Installed on 2020-04-27 (20 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/20/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F4 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: Z170X-Gaming 3 dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF4:bd10/20/2015:svnGigabyteTechnologyCo.,Ltd.:pnZ170X-Gaming3:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnZ170X-Gaming3:rvrx.x:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: Z170X-Gaming 3 dmi.product.sku: To be filled by O.E.M. dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: Gigabyte Technology Co., Ltd. modified.conffile..etc.pulse.default.pa: [modified] mtime.conffile..etc.pulse.default.pa: 2020-05-17T19:59:02.590821 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1879182/+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 1879352] [NEW] /usr/bin/im-launch i3 fails
Public bug reported: Trying to run i3 in Focal Fossa, login fails. The screen goes black briefly, then returns to the login screen. I expect this is reproducible by just installing `i3`, selecting it on the settings in the login screen, and logging in. I see the following in the log: ``` May 18 11:32:21 hopper /usr/lib/gdm3/gdm-x-session[4733]: /etc/X11/Xsession.d/99x11-common_start: line 5: /usr/bin/im-launch i3: No such file or directory ``` Editing that file to just run `/usr/bin/im-launch i3` works fine. Is this some kind of shell quoting issue, where it's trying to execve that full string? I believe this is in the `x11-common` package: ``` hopper ~ $ dpkg -S /etc/X11/Xsession.d/99x11-common_start x11-common: /etc/X11/Xsession.d/99x11-common_start ``` but Launchpad complains that such a thing does not exist. Perhaps I misunderstand "package". ** Affects: xorg (Ubuntu) Importance: Undecided Status: New -- 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/1879352 Title: /usr/bin/im-launch i3 fails Status in xorg package in Ubuntu: New Bug description: Trying to run i3 in Focal Fossa, login fails. The screen goes black briefly, then returns to the login screen. I expect this is reproducible by just installing `i3`, selecting it on the settings in the login screen, and logging in. I see the following in the log: ``` May 18 11:32:21 hopper /usr/lib/gdm3/gdm-x-session[4733]: /etc/X11/Xsession.d/99x11-common_start: line 5: /usr/bin/im-launch i3: No such file or directory ``` Editing that file to just run `/usr/bin/im-launch i3` works fine. Is this some kind of shell quoting issue, where it's trying to execve that full string? I believe this is in the `x11-common` package: ``` hopper ~ $ dpkg -S /etc/X11/Xsession.d/99x11-common_start x11-common: /etc/X11/Xsession.d/99x11-common_start ``` but Launchpad complains that such a thing does not exist. Perhaps I misunderstand "package". To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1879352/+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 1879182] Re: Sound cuts off and back on randomly during online streaming of videos
Thanks for the reply. Over amplification is already off. No process takes more than 12% CPU utilization. -- 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/1879182 Title: Sound cuts off and back on randomly during online streaming of videos Status in pulseaudio package in Ubuntu: Incomplete Bug description: Sound shuts off and turns back on again with two pop clicks. When the sound is off, if i turn up the volume to the max, i can hear crackling sound in speakers in tune with sound playing on the computer. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: pulseaudio 1:13.99.1-1ubuntu3.2 ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30 Uname: Linux 5.4.0-29-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: siddahuja 31829 F pulseaudio /dev/snd/controlC0: siddahuja 31829 F pulseaudio /dev/snd/pcmC0D0p: siddahuja 31829 F...m pulseaudio /dev/snd/timer: siddahuja 31829 f pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sun May 17 23:56:27 2020 InstallationDate: Installed on 2020-04-27 (20 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/20/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F4 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: Z170X-Gaming 3 dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF4:bd10/20/2015:svnGigabyteTechnologyCo.,Ltd.:pnZ170X-Gaming3:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnZ170X-Gaming3:rvrx.x:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: Z170X-Gaming 3 dmi.product.sku: To be filled by O.E.M. dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: Gigabyte Technology Co., Ltd. modified.conffile..etc.pulse.default.pa: [modified] mtime.conffile..etc.pulse.default.pa: 2020-05-17T19:59:02.590821 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1879182/+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 1875493] Re: [core] log rotation doesn't properly restart rsyslogd
@ogra If the component in question was removed and/or deprecated and no longer used in the current development release, then the policy shouldn't apply. In this case I don't think it would be much of a stretch to get a waiver for this. That said, as I'm pretty sure this bug is specific to Core, so fixing the issue in the core snap directly is probably the better approach. We can't just leave things "as is", as this bug can lead to Core devices running out of storage. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to rsyslog in Ubuntu. https://bugs.launchpad.net/bugs/1875493 Title: [core] log rotation doesn't properly restart rsyslogd Status in Snappy: New Status in rsyslog package in Ubuntu: New Bug description: One of our commercial partners is developing a device agent snap for UC16. One of their engineers just shared the following bug report: I wanted to give you a heads up on an issue that we encountered with one of our gateways (a Dell 3000) regarding a full disk (/writable). It seems as though rsyslog had a bad logrotate config and was holding on to deleted files as described here: - https://www.claudiokuenzler.com/blog/861/after-ubuntu-update-trusty-xenial-disk-filled-syslog-logrotate - https://bugzilla.redhat.com/show_bug.cgi?id=1713358 Both df and du where showing different results for the “/writable” path on the Dell gateway. We were able to copy the lsof binary over and found this: $ sudo /tmp/lsof | grep deleted ... rsyslogd 1765 syslog 5w REG 179,4 1993793536 130599 /var/log/syslog (deleted) rsyslogd 1765 syslog 6w REG 179,4 45056 130836 /var/log/auth.log (deleted) rsyslogd 1765 syslog 7w REG 179,4 211976192 130782 /var/log/kern.log (deleted) in:imuxso 1765 1776 syslog 5w REG 179,4 1993793536 130599 /var/log/syslog (deleted) in:imuxso 1765 1776 syslog 6w REG 179,4 45056 130836 /var/log/auth.log (deleted) in:imuxso 1765 1776 syslog 7w REG 179,4 211976192 130782 /var/log/kern.log (deleted) in:imklog 1765 1777 syslog 5w REG 179,4 1993793536 130599 /var/log/syslog (deleted) in:imklog 1765 1777 syslog 6w REG 179,4 45056 130836 /var/log/auth.log (deleted) in:imklog 1765 1777 syslog 7w REG 179,4 211976192 130782 /var/log/kern.log (deleted) rs:main 1765 1778 syslog 5w REG 179,4 1993793536 130599 /var/log/syslog (deleted) rs:main 1765 1778 syslog 6w REG 179,4 45056 130836 /var/log/auth.log (deleted) rs:main 1765 1778 syslog 7w REG 179,4 211976192 130782 /var/log/kern.log (deleted) ... Restarting the service freed up the deleted files / disk space: sudo service rsyslog restart The rsyslog config (/etc/logrotate.d/rsyslog) calls this script post rotate: /usr/lib/rsyslog/rsyslog-rotate Which does not actually kill the rsyslog process: admin@GR0GP42:~$ ps aux | grep rsyslog syslog 2305 0.7 0.1 262692 3432 ? Ssl 20:35 0:00 /usr/sbin/rsyslogd -n admin 2464 0.0 0.0 12984 932 pts/0 S+ 20:36 0:00 grep --color=auto rsyslog admin@GR0GP42:~$ sudo /usr/lib/rsyslog/rsyslog-rotate admin@GR0GP42:~$ ps aux | grep rsyslog syslog 2305 0.6 0.1 262692 3432 ? Ssl 20:35 0:00 /usr/sbin/rsyslogd -n admin 2469 0.0 0.0 12984 972 pts/0 S+ 20:36 0:00 grep --color=auto rsyslog The fix appears to be using the following command: sudo systemctl restart rsyslog >/dev/null 2>&1 || true admin@GR0GP42:~$ ps aux | grep rsyslog syslog 2305 0.6 0.1 262692 3432 ? Ssl 20:35 0:00 /usr/sbin/rsyslogd -n admin 2482 0.0 0.0 12984 972 pts/0 S+ 20:36 0:00 grep --color=auto rsyslog admin@GR0GP42:~$ sudo systemctl restart rsyslog >/dev/null 2>&1 || true admin@GR0GP42:~$ ps aux | grep rsyslog syslog 2487 1.0 0.1 262692 3432 ? Ssl 20:36 0:00 /usr/sbin/rsyslogd -n admin 2496 0.0 0.0 12984 980 pts/0 S+ 20:36 0:00 grep --color=auto rsyslog To manage notifications about this bug go to: https://bugs.launchpad.net/snappy/+bug/1875493/+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 1878752] Re: vgcreate fails on /dev/disk/by-dname block devices
I would very much agree with xnox (it's a duplicate) (and Dan, nothing
for curtin to do);
curtin generated dname rules rely upon pointing to a /dev/bcache/by-
uuid/* symlink which is currently broken per
https://bugs.launchpad.net/ubuntu/+source/linux-signed/+bug/1861941
which at this time points some issue in udev itself (the kernel emits
all of the correct uevents we expect).
And as James' workaround shows; it's *not* always happening; a rescan
can "restore" the links; but that's not 100% reliable.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lvm2 in Ubuntu.
https://bugs.launchpad.net/bugs/1878752
Title:
vgcreate fails on /dev/disk/by-dname block devices
Status in OpenStack ceph-osd charm:
New
Status in curtin package in Ubuntu:
Invalid
Status in lvm2 package in Ubuntu:
New
Bug description:
Ubuntu Focal, OpenStack Charmers Next Charms.
juju run-action --wait ceph-osd/0 add-disk osd-devices=/dev/disk/by-
dname/bcache2
unit-ceph-osd-0:
UnitId: ceph-osd/0
id: "5"
message: exit status 1
results:
ReturnCode: 1
Stderr: |
partx: /dev/disk/by-dname/bcache2: failed to read partition table
Failed to find physical volume "/dev/bcache1".
Failed to find physical volume "/dev/bcache1".
Device /dev/disk/by-dname/bcache2 not found.
Traceback (most recent call last):
File "/var/lib/juju/agents/unit-ceph-osd-0/charm/actions/add-disk",
line 79, in
request = add_device(request=request,
File "/var/lib/juju/agents/unit-ceph-osd-0/charm/actions/add-disk",
line 34, in add_device
charms_ceph.utils.osdize(device_path, hookenv.config('osd-format'),
File "lib/charms_ceph/utils.py", line 1497, in osdize
osdize_dev(dev, osd_format, osd_journal,
File "lib/charms_ceph/utils.py", line 1570, in osdize_dev
cmd = _ceph_volume(dev,
File "lib/charms_ceph/utils.py", line 1705, in _ceph_volume
cmd.append(_allocate_logical_volume(dev=dev,
File "lib/charms_ceph/utils.py", line 1965, in
_allocate_logical_volume
lvm.create_lvm_volume_group(vg_name, pv_dev)
File "hooks/charmhelpers/contrib/storage/linux/lvm.py", line 104, in
create_lvm_volume_group
check_call(['vgcreate', volume_group, block_device])
File "/usr/lib/python3.8/subprocess.py", line 364, in check_call
raise CalledProcessError(retcode, cmd)
subprocess.CalledProcessError: Command '['vgcreate',
'ceph-911bc34b-4634-4ebd-a055-876b978d0b0a', '/dev/disk/by-dname/bcache2']'
returned non-zero exit status 5.
Stdout: |2
Physical volume "/dev/disk/by-dname/bcache2" successfully created.
status: failed
timing:
completed: 2020-05-15 06:04:41 + UTC
enqueued: 2020-05-15 06:04:30 + UTC
started: 2020-05-15 06:04:39 + UTC
The same action on the /dev/bcacheX device succeeds - looks like some
sort of behaviour break in Ubuntu.
To manage notifications about this bug go to:
https://bugs.launchpad.net/charm-ceph-osd/+bug/1878752/+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 1879343] [NEW] REGRESSION - Ctrl+Alt+F1 no longer gives me access to virtual terminal, just a black screen
Public bug reported: Ctrl+Alt+F1 used to give you access to a cirtual terminal, or virtual console, not entirely sure what that's called, where you can log in into a shell and run commands. I use that when some of the tons of bugs in Ubuntu makes the system hang so badly that I can't even open a terminal window, in order to figure out if there's a process that I can kill. Then I'd be able to return to the xorg screen with Ctrl+Alt+F7. Now (and even while the system is not hung at all) I'm doing ctrl+Alt+F1, and all I get is a black screen with no console/terminal at all. Completely fucking useless, ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3.1 ProcVersionSignature: Ubuntu 4.4.0-173.203-generic 4.4.208 Uname: Linux 4.4.0-173-generic x86_64 NonfreeKernelModules: nvidia_uvm 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.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 340.107 Thu May 24 21:54:01 PDT 2018 GCC version: gcc version 5.4.0 20160609 (Ubuntu 5.4.0-6ubuntu1~16.04.12) .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.23 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Mon May 18 17:02:03 2020 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu ExtraDebuggingInterest: No GraphicsCard: Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Acer Incorporated [ALI] 3rd Gen Core processor Graphics Controller [1025:0647] NVIDIA Corporation GF117M [GeForce 610M/710M/810M/820M / GT 620M/625M/630M/720M] [10de:1140] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Acer Incorporated [ALI] GeForce 710M [1025:0691] InstallationDate: Installed on 2013-10-11 (2410 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) MachineType: Acer Aspire V3-571G ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-173-generic root=UUID=5830b30e-69e8-4bb4-8a2b-bc2b43c7414a ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/15/2012 dmi.bios.vendor: Acer dmi.bios.version: V2.07 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: VA50_HC_CR dmi.board.vendor: Acer dmi.board.version: Type2 - Board Version dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: V2.07 dmi.modalias: dmi:bvnAcer:bvrV2.07:bd10/15/2012:svnAcer:pnAspireV3-571G:pvrV2.07:rvnAcer:rnVA50_HC_CR:rvrType2-BoardVersion:cvnAcer:ct10:cvrV2.07: dmi.product.name: Aspire V3-571G dmi.product.version: V2.07 dmi.sys.vendor: Acer version.compiz: compiz 1:0.9.12.3+16.04.20180221-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.91-2~16.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~16.04.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~16.04.1 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.8 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20160325-1ubuntu1.2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2 xserver.bootTime: Fri Apr 17 02:39:40 2020 xserver.configfile: /etc/X11/xorg.conf xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.18.4-0ubuntu0.8 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug compiz-0.9 third-party-packages ubuntu xenial -- 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/1879343 Title: REGRESSION - Ctrl+Alt+F1 no longer gives me access to virtual terminal, just a black screen Status in xorg package in Ubuntu: New Bug description: Ctrl+Alt+F1 used to give you access to a cirtual terminal, or virtual console, not entirely sure what that's called, where you can log in into a shell and run commands. I use that when some of the tons of bugs in Ubuntu makes the system hang so badly that I can't even open a terminal window, in order to figure out if there's a process that I can kill. Then I'd be able to return to the xorg screen with Ctrl+Alt+F7. Now (and even while the system is not hung at all) I'm doing ctrl+Alt+F1, and all I get is a black screen with no console/terminal at all. Completely fucking useless, ProblemType: Bug
[Touch-packages] [Bug 1879058] Re: Display viewport incorrect with 90° rotated displayed
** Package changed: ubuntu => xorg (Ubuntu) -- 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/1879058 Title: Display viewport incorrect with 90° rotated displayed Status in xorg package in Ubuntu: New Bug description: The system which automatically configure the position and size of the display seems to not handle the display viewport correctly. When configuring the position of displays with Ubuntu display settings interface, If I set a vertical display (rotated 90°) for a 1920x1080 display, then it seems the viewport or virtual display (I don't really know how you name is) seems to be 1920x1920. So the desktop is bigger than the screen and it can be moved with the mouse. Considering I use multi screens (3 rotated and one normal) it makes some crazy things. So my feeling is that while the screen is rotated, the viewport definition remains 1920x1080 instead of 1080x1920, and the system resolve it by providing a viewport of 1920x1920. This issue can be more or less circumvented using Nvidia Tools to configure displays. With it, the viewport seems to work correctly. However, as soon as a screen is disconnected, the system reconfigure the various displays and the issue comes back. So often, after a sleep or something like that, the issue comes back. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1879058/+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 1879058] [NEW] Display viewport incorrect with 90° rotated displayed
You have been subscribed to a public bug: The system which automatically configure the position and size of the display seems to not handle the display viewport correctly. When configuring the position of displays with Ubuntu display settings interface, If I set a vertical display (rotated 90°) for a 1920x1080 display, then it seems the viewport or virtual display (I don't really know how you name is) seems to be 1920x1920. So the desktop is bigger than the screen and it can be moved with the mouse. Considering I use multi screens (3 rotated and one normal) it makes some crazy things. So my feeling is that while the screen is rotated, the viewport definition remains 1920x1080 instead of 1080x1920, and the system resolve it by providing a viewport of 1920x1920. This issue can be more or less circumvented using Nvidia Tools to configure displays. With it, the viewport seems to work correctly. However, as soon as a screen is disconnected, the system reconfigure the various displays and the issue comes back. So often, after a sleep or something like that, the issue comes back. ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: bot-comment x11 -- Display viewport incorrect with 90° rotated displayed https://bugs.launchpad.net/bugs/1879058 You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg 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 1878752] Re: vgcreate fails on /dev/disk/by-dname block devices
This doesn't seem to be a curtin bug to me; feel free to disagree (with
reasoning!).
** Changed in: curtin (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lvm2 in Ubuntu.
https://bugs.launchpad.net/bugs/1878752
Title:
vgcreate fails on /dev/disk/by-dname block devices
Status in OpenStack ceph-osd charm:
New
Status in curtin package in Ubuntu:
Invalid
Status in lvm2 package in Ubuntu:
New
Bug description:
Ubuntu Focal, OpenStack Charmers Next Charms.
juju run-action --wait ceph-osd/0 add-disk osd-devices=/dev/disk/by-
dname/bcache2
unit-ceph-osd-0:
UnitId: ceph-osd/0
id: "5"
message: exit status 1
results:
ReturnCode: 1
Stderr: |
partx: /dev/disk/by-dname/bcache2: failed to read partition table
Failed to find physical volume "/dev/bcache1".
Failed to find physical volume "/dev/bcache1".
Device /dev/disk/by-dname/bcache2 not found.
Traceback (most recent call last):
File "/var/lib/juju/agents/unit-ceph-osd-0/charm/actions/add-disk",
line 79, in
request = add_device(request=request,
File "/var/lib/juju/agents/unit-ceph-osd-0/charm/actions/add-disk",
line 34, in add_device
charms_ceph.utils.osdize(device_path, hookenv.config('osd-format'),
File "lib/charms_ceph/utils.py", line 1497, in osdize
osdize_dev(dev, osd_format, osd_journal,
File "lib/charms_ceph/utils.py", line 1570, in osdize_dev
cmd = _ceph_volume(dev,
File "lib/charms_ceph/utils.py", line 1705, in _ceph_volume
cmd.append(_allocate_logical_volume(dev=dev,
File "lib/charms_ceph/utils.py", line 1965, in
_allocate_logical_volume
lvm.create_lvm_volume_group(vg_name, pv_dev)
File "hooks/charmhelpers/contrib/storage/linux/lvm.py", line 104, in
create_lvm_volume_group
check_call(['vgcreate', volume_group, block_device])
File "/usr/lib/python3.8/subprocess.py", line 364, in check_call
raise CalledProcessError(retcode, cmd)
subprocess.CalledProcessError: Command '['vgcreate',
'ceph-911bc34b-4634-4ebd-a055-876b978d0b0a', '/dev/disk/by-dname/bcache2']'
returned non-zero exit status 5.
Stdout: |2
Physical volume "/dev/disk/by-dname/bcache2" successfully created.
status: failed
timing:
completed: 2020-05-15 06:04:41 + UTC
enqueued: 2020-05-15 06:04:30 + UTC
started: 2020-05-15 06:04:39 + UTC
The same action on the /dev/bcacheX device succeeds - looks like some
sort of behaviour break in Ubuntu.
To manage notifications about this bug go to:
https://bugs.launchpad.net/charm-ceph-osd/+bug/1878752/+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 1326536] Re: libvirt's dnsmasq setup will read /etc/hosts on the host, resulting in odd resolution behaviour on the VM
This bug is still present in ubuntu 20.04. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/1326536 Title: libvirt's dnsmasq setup will read /etc/hosts on the host, resulting in odd resolution behaviour on the VM Status in libvirt package in Ubuntu: Triaged Status in lxc package in Ubuntu: Triaged Bug description: When libvirt configures / starts up dnsmasq on the host, it does not pass --no-hosts, resulting in it reading in the /etc/hosts file from the host. The default ubuntu setup will have the host's hostname in /etc/hosts under 127.0.1.1. Since libvirt's dnsmasq is reading this file, anything querying that dnsmasq instance will resolve the host's hostname out of /etc/hosts. The result of this is any VM running on the host will resolve the host's hostname as 127.0.1.1. For example, if the host's hostname is BoxA, any VM running on the host will resolve BoxA to 127.0.1.1, which is not BoxA's actual address. Would recommend passing --no-hosts to dnsmasq when libvirt starts it up. If a user wants hardcoded hosts for their libvirt network, they can add them to /var/lib/libvirt/dnsmasq/default.addnhosts . If this is an acceptable solution, I'd be happy to write the patch up. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1326536/+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 1698388] Re: Assertion failure in journal-remote-parse.c
Fixed in Bionic and later. ** Also affects: systemd (Ubuntu Xenial) Importance: Undecided Status: New ** Changed in: systemd (Ubuntu) Status: New => Fix Released ** Changed in: systemd (Ubuntu Xenial) Status: New => Confirmed -- 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/1698388 Title: Assertion failure in journal-remote-parse.c Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Xenial: Confirmed Bug description: I am observing the following assertion failure in systemd-journal- remote: Assertion 'source->filled <= source->size' failed at ../src/journal- remote/journal-remote-parse.c:95, function get_line(). Aborting. Systemd version: systemd 229 +PAM +AUDIT +SELINUX +IMA +APPARMOR +SMACK +SYSVINIT +UTMP +LIBCRYPTSETUP +GCRYPT +GNUTLS +ACL +XZ -LZ4 +SECCOMP +BLKID +ELFUTILS +KMOD -IDN Ubuntu release: Description: Ubuntu 16.04.1 LTS Release: 16.04 Package version: systemd: Installed: 229-4ubuntu13 Candidate: 229-4ubuntu17 It looks like this issue has been fixed upstream in v230, specifically in commit 9ba37525d0ef3d144a50ed5fd4710573e92b7ec1. Could this particular commit be backported? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1698388/+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 1879333] [NEW] Black screen on loading latest system update
Public bug reported: This bug has been around since 16.04 and still occurs with 18.04 when using nvidia drivers. When update required for the OS the black screen situation happens after the required reboot. Only way to regain desktop is to login via ssh terminal and run the commands listed here: https://askubuntu.com/questions/1129516/black-screen-at-boot-after- nvidia-driver-installation-on-ubuntu-18-04-2-lts sudo apt-get update sudo apt-get upgrade sudo apt-get purge nvidia* sudo apt autoremove sudo apt-get install dkms build-essential linux-headers-$(uname -r) echo "# Disable the default Nouveau kernel driver" | sudo tee -a /etc/modprobe.d/blacklist-nouveau.conf echo "# -" | sudo tee -a /etc/modprobe.d/blacklist-nouveau.conf echo "blacklist nouveau" | sudo tee -a /etc/modprobe.d/blacklist- nouveau.conf echo "blacklist lbm-nouveau" | sudo tee -a /etc/modprobe.d/blacklist- nouveau.conf echo "options nouveau modeset=0" | sudo tee -a /etc/modprobe.d /blacklist-nouveau.conf echo "alias nouveau off" | sudo tee -a /etc/modprobe.d/blacklist- nouveau.conf echo "alias lbm-nouveau off" | sudo tee -a /etc/modprobe.d/blacklist- nouveau.conf cat /etc/modprobe.d/blacklist-nouveau.conf echo "options nouveau modeset=0" | sudo tee -a /etc/modprobe.d/nouveau- kms.conf cat /etc/modprobe.d/nouveau-kms.conf sudo update-initramfs -u sudo service lightdm stop sudo apt-get install nvidia-driver-440 lsmod | grep nvidia sudo lshw -c video | grep 'configuration' sudo reboot ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-101.102-generic 4.15.18 Uname: Linux 4.15.0-101-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.14 Architecture: amd64 BootLog: CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' Date: Mon May 18 08:44:05 2020 DistUpgraded: 2019-12-17 11:35:32,743 DEBUG icon theme changed, re-reading DistroCodename: bionic DistroVariant: ubuntu DkmsStatus: bbswitch, 0.8, 4.15.0-101-generic, x86_64: installedError! Could not locate dkms.conf file. File: does not exist. bbswitch, 0.8, 4.15.0-99-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Subsystem: ASRock Incorporation Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx Integrated Graphics Controller [1849:22b1] NVIDIA Corporation GK208 [GeForce GT 630 Rev. 2] [10de:1284] (rev a1) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. GK208 [GeForce GT 630 Rev. 2] [1043:846a] InstallationDate: Installed on 2019-09-26 (234 days ago) InstallationMedia: Ubuntu 16.04.6 LTS "Xenial Xerus" - Release amd64 (20190227) MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-101-generic root=UUID=89ea4739-64a1-4200-9626-c597e9d5a485 ro quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to bionic on 2019-12-17 (152 days ago) dmi.bios.date: 02/27/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P1.50 dmi.board.name: N3150M 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.:bvrP1.50:bd02/27/2018:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnN3150M: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.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1 version.libdrm2: libdrm2 2.4.99-1ubuntu1~18.04.2 version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.8-0ubuntu0~18.04.3 version.libgl1-mesa-glx: libgl1-mesa-glx 19.2.8-0ubuntu0~18.04.3 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.4 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 xserver.bootTime: Wed Apr 29 07:15:33 2020 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: xserver.version: 2:1.19.6-1ubuntu4.4 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic ubuntu -- 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/1879333 Title: Black screen on loading latest system update Status in xorg package in Ubuntu: New Bug description: This bug has been around since 16.04
[Touch-packages] [Bug 1879090] Re: XDG_SEAT, XDG_VTNR, XDG_SESSION_ID not set
Thank you for responding. I wonder if it's intended by design. I used to logout via `dbus-send --system --print-reply --dest=org.freedesktop.login1 /org/freedesktop/login1 'org.freedesktop.login1.Manager.TerminateSession' string:$XDG_SESSION_ID` or `loginctl kill-session $XDG_SESSION_ID` in my scripts. I can live without them. Did developers drop those environment variables? Another question: Is that issue related to `lightdm` or `systemd`? Regards. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1879090 Title: XDG_SEAT, XDG_VTNR, XDG_SESSION_ID not set Status in lightdm package in Ubuntu: Incomplete Bug description: I installed Ubuntu 20.04, it is running well. I switched display manager to lightdm. I noticed that it fails to set environment variables XDG_SEAT, XDG_VTNR, XDG_SESSION_ID. I also tested gdm3, it's the same. I also tried liveiso to no vail. apt-cache policy lightdm lightdm: Installed: 1.30.0-0ubuntu3.1 Candidate: 1.30.0-0ubuntu3.1 Version table: *** 1.30.0-0ubuntu3.1 500 500 http://archive.ubuntu.com/ubuntu focal/universe amd64 Packages 100 /var/lib/dpkg/status To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1879090/+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 1826003] Re: software properties unknown to ubuntu software
Problem disappeared. changed status to invalid ** Changed in: software-properties (Ubuntu) Status: New => Invalid -- 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/1826003 Title: software properties unknown to ubuntu software Status in software-properties package in Ubuntu: Invalid Bug description: open the dash, right click on 'software properties' select 'show details' gnome software opens with a message 'unable to find "software-properties-gtk.desktop" corrado@corrado-HP-p4-ee:~$ inxi -Fx System:Host: corrado-HP-p4-ee Kernel: 5.0.0-13-generic x86_64 bits: 64 compiler: gcc v: 8.3.0 Desktop: Gnome 3.32.0 Distro: Ubuntu 19.10 (Eoan EANIMAL) Machine: Type: Laptop System: Hewlett-Packard product: HP 250 G3 Notebook PC v: 0991100600087 serial: Mobo: Hewlett-Packard model: 2211 v: 86.49 serial: UEFI: Insyde v: F.36 date: 12/18/2014 Battery: ID-1: BAT1 charge: 16.0 Wh condition: 20.0/20.0 Wh (100%) model: 13-42 OA03031 status: Discharging CPU: Topology: Dual Core model: Intel Core i5-4210U bits: 64 type: MT MCP arch: Haswell rev: 1 L2 cache: 3072 KiB flags: lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx bogomips: 19156 Speed: 798 MHz min/max: 800/2700 MHz Core speeds (MHz): 1: 798 2: 798 3: 798 4: 798 Graphics: Device-1: Intel Haswell-ULT Integrated Graphics vendor: Hewlett-Packard driver: i915 v: kernel bus ID: 00:02.0 Display: x11 server: X.Org 1.20.4 driver: i915 resolution: 1366x768~60Hz OpenGL: renderer: Mesa DRI Intel Haswell Mobile v: 4.5 Mesa 19.0.2 direct render: Yes Audio: Device-1: Intel Haswell-ULT HD Audio vendor: Hewlett-Packard driver: snd_hda_intel v: kernel bus ID: 00:03.0 Device-2: Intel 8 Series HD Audio vendor: Hewlett-Packard driver: snd_hda_intel v: kernel bus ID: 00:1b.0 Sound Server: ALSA v: k5.0.0-13-generic Network: Device-1: Realtek RTL810xE PCI Express Fast Ethernet vendor: Hewlett-Packard driver: r8169 v: kernel port: 3000 bus ID: 08:00.0 IF: enp8s0 state: down mac: 5c:b9:01:06:ba:ce Device-2: Ralink RT3290 Wireless 802.11n 1T/1R PCIe vendor: Hewlett-Packard driver: rt2800pci v: 2.3.0 port: 3000 bus ID: 09:00.0 IF: wlp9s0f0 state: up mac: ac:d1:b8:82:03:5d Drives:Local Storage: total: 465.76 GiB used: 5.88 GiB (1.3%) ID-1: /dev/sda vendor: Seagate model: ST500LT012-1DG142 size: 465.76 GiB Partition: ID-1: / size: 31.25 GiB used: 5.87 GiB (18.8%) fs: ext4 dev: /dev/sda4 ID-2: swap-1 size: 4.00 GiB used: 0 KiB (0.0%) fs: swap dev: /dev/sda2 Sensors: System Temperatures: cpu: 41.0 C mobo: N/A Fan Speeds (RPM): N/A Info: Processes: 209 Uptime: 2h 44m Memory: 3.78 GiB used: 1.14 GiB (30.0%) Init: systemd runlevel: 5 Compilers: gcc: 8.3.0 Shell: bash v: 5.0.3 inxi: 3.0.33 corrado@corrado-HP-p4-ee:~$ locale LANG=en_US.UTF-8 LANGUAGE= LC_CTYPE="en_US.UTF-8" LC_NUMERIC=it_IT.UTF-8 LC_TIME=it_IT.UTF-8 LC_COLLATE="en_US.UTF-8" LC_MONETARY=it_IT.UTF-8 LC_MESSAGES="en_US.UTF-8" LC_PAPER=it_IT.UTF-8 LC_NAME=it_IT.UTF-8 LC_ADDRESS=it_IT.UTF-8 LC_TELEPHONE=it_IT.UTF-8 LC_MEASUREMENT=it_IT.UTF-8 LC_IDENTIFICATION=it_IT.UTF-8 LC_ALL= corrado@corrado-HP-p4-ee:~$ ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: gnome-software 3.30.6-2ubuntu3 ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6 Uname: Linux 5.0.0-13-generic x86_64 ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Apr 23 17:13:53 2019 ExecutablePath: /usr/bin/gnome-software InstallationDate: Installed on 2019-04-21 (1 days ago) InstallationMedia: Ubuntu 19.10 "Eoan EANIMAL" - Alpha amd64 (20190421) InstalledPlugins: gnome-software-plugin-flatpak N/A gnome-software-plugin-snap3.30.6-2ubuntu3 SourcePackage: gnome-software UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1826003/+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 1879144] Re: Volume output settings reset on analog surround 4.0
There is one thing I am not sure: it is an issue of pulseaudio or an issue of the ubuntu settings. But I will upstream it though. -- 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/1879144 Title: Volume output settings reset on analog surround 4.0 Status in pulseaudio package in Ubuntu: New Bug description: It seems to be a pulseaudio issue but unsure if it is a settings error. Version: Ubuntu 20.04 LTS / 20.04 Computer Model: HP Envy x360 13 with AMD Ryzen 3500U PulseAudio version: 1:13.99.1-1ubuntu3.2 Problem Description: When manually reduce volume, Balance and Fade level resets when such reduction reaches 0 audio output. This is not the case when I manually mute the audio output (or with a mute switch) Intended Outcome: There should not be any reset at all. Other information: It seems to be a problem with pulseaudio. However, I cannot confirm if it is a bug from the pulseaudio side or the Ubuntu settings side. Intended outcome: It should work the same: turning the volume to 0 should not reset the fade settings nor the balance settings. Check the screencast below for what is going on (youtube link) (0:00-0:22): https://www.youtube.com/watch?v=EEsClQ7Pj08 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1879144/+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 1164016] Re: restore type-ahead find
SEARCHING IS NOT NAVIGATING, please. Besides the debate on whether the option to disable search when starting to type should exist (I think it should), #144 has raised quite an important side effect: searching should not make it look like files are deleted. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-settings in Ubuntu. https://bugs.launchpad.net/bugs/1164016 Title: restore type-ahead find Status in Nautilus: Expired Status in nautilus package in Ubuntu: Fix Released Status in ubuntu-settings package in Ubuntu: Fix Released Bug description: GNOME removed type-ahead find in Nautilus 3.6, not without controversy: https://mail.gnome.org/archives/nautilus- list/2012-August/msg2.html Now when you type in a Nautilus window, Nautilus immediately performs a search in the current directory and all its subdirectories. I personally find this annoying. If I want to search, I'll click the search icon. Often I'm looking at a long directory listing and simply want to jump to a certain point in it, and type-ahead find works great for that. Would Ubuntu consider patching type-ahead find back in? To manage notifications about this bug go to: https://bugs.launchpad.net/nautilus/+bug/1164016/+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 1871763] Re: Duplicity is not working
** Changed in: duplicity Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to python-defaults in Ubuntu. https://bugs.launchpad.net/bugs/1871763 Title: Duplicity is not working Status in Duplicity: Invalid Status in python-defaults package in Ubuntu: New Bug description: Duplicity is failing to make backup. It produces error message: see attached 000_Error_message.png After starting duplicity from terminal, I got much better error message: unim95@ubuntu-BitFenix-Prodigy:~$ duplicity bash: /usr/bin/duplicity: /usr/bin/python2: bad interpreter: No such file or directory After searching system for python2 i found, that there is no python2 executable unim95@ubuntu-BitFenix-Prodigy:~$ locate python2 | grep -v lib | grep -v man | grep -v doc | grep -v include /etc/python2.7 /etc/python2.7/sitecustomize.py /snap/core/8689/usr/share/bash-completion/completions/python2 /snap/core/8689/usr/share/dh-python/dh_python2 /snap/core/8689/usr/share/dh-python/dist/cpython2_fallback /snap/core/8935/usr/share/bash-completion/completions/python2 /snap/core/8935/usr/share/dh-python/dh_python2 /snap/core/8935/usr/share/dh-python/dist/cpython2_fallback /usr/bin/python2-futurize /usr/bin/python2-pasteurize /usr/bin/python2.7 /usr/bin/python2.7-config /usr/bin/waitress-serve-python2 /usr/bin/x86_64-linux-gnu-python2.7-config /usr/share/app-install/desktop/idle-python2.7:idle-python2.7.desktop /usr/share/applications/python2.7.desktop /usr/share/bash-completion/completions/python2 /usr/share/binfmts/python2.7 /usr/share/dh-python/dh_python2 /usr/share/dh-python/dist/cpython2_fallback /usr/share/lintian/overrides/python2.7 /usr/share/lintian/overrides/python2.7-minimal /usr/share/pixmaps/python2.7.xpm Default python is: unim95@ubuntu-BitFenix-Prodigy:~$ python --version Python 2.7.17 Duplicity version: unim95@ubuntu-BitFenix-Prodigy:~$ dpkg -s duplicity Package: duplicity Status: install ok installed Priority: optional Section: utils Installed-Size: 1064 Maintainer: Ubuntu Developers Architecture: amd64 Version: 0.7.17-0ubuntu1.1 Depends: libc6 (>= 2.4), librsync1 (>= 0.9.6), python (<< 2.8), python (>= 2.7~), python-fasteners, python:any (<< 2.8), python:any (>= 2.7.5-5~), python-lockfile (>> 1:0.9), gnupg | gnupg1 Suggests: rsync, python-paramiko, python-pexpect, python-urllib3, python-oauthlib, python-boto, ncftp, python-cloudfiles, lftp, python-gdata, tahoe-lafs, python-swiftclient Description: encrypted bandwidth-efficient backup Duplicity backs directories by producing encrypted tar-format volumes and uploading them to a remote or local file server. Because duplicity uses librsync, the incremental archives are space efficient and only record the parts of files that have changed since the last backup. Because duplicity uses GnuPG to encrypt and/or sign these archives, they will be safe from spying and/or modification by the server. Homepage: http://duplicity.nongnu.org/ Original-Maintainer: Alexander Zangerl Python2 version: unim95@ubuntu-BitFenix-Prodigy:~$ dpkg -s python Package: python Status: install ok installed Priority: optional Section: python Installed-Size: 624 Maintainer: Ubuntu Developers Architecture: amd64 Multi-Arch: allowed Source: python-defaults Version: 2.7.15~rc1-1 Replaces: python-dev (<< 2.6.5-2) Provides: python-ctypes, python-email, python-importlib, python-profiler, python-wsgiref Depends: python2.7 (>= 2.7.15~rc1-1~), libpython-stdlib (= 2.7.15~rc1-1) Pre-Depends: python-minimal (= 2.7.15~rc1-1) Suggests: python-doc (= 2.7.15~rc1-1), python-tk (>= 2.7.15~rc1-1~) Breaks: update-manager-core (<< 0.200.5-2) Conflicts: python-central (<< 0.5.5) Description: interactive high-level object-oriented language (default version) Python, the high-level, interactive object oriented language, includes an extensive class library with lots of goodies for network programming, system administration, sounds and graphics. . This package is a dependency package, which depends on Debian's default Python version (currently v2.7). Original-Maintainer: Matthias Klose Homepage: http://www.python.org/ Cnf-Extra-Commands: python Cnf-Priority-Bonus: 3 OS: unim95@ubuntu-BitFenix-Prodigy:~$ cat /etc/os-release NAME="Ubuntu" VERSION="18.04.4 LTS (Bionic Beaver)" ID=ubuntu ID_LIKE=debian PRETTY_NAME="Ubuntu 18.04.4 LTS" VERSION_ID="18.04" HOME_URL="https://www.ubuntu.com/; SUPPORT_URL="https://help.ubuntu.com/; BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/; PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies/privacy-policy; VERSION_CODENAME=bionic UBUNTU_CODENAME=bionic FS used: ext4. To manage notifications about this bug go to:
[Touch-packages] [Bug 1879326] [NEW] DNS resolution ceased to work after update
Public bug reported: Hi I did a Focal install on 14th of May 2020, could work until in the night of 16th of May 2020 and in the morning of the 18th of May 2020 I could not resolve domain names anymore. I can ping DNS servers but the resolution to IP addresses fails. I have switched on automatic installation of security relevant updates. I can reproduce the behaviour with a fresh install accepting all the updates there are. I did not try to find out which update is the cause. See the behaviour below where I even have tried to work around by removing the DNS server of my router: thiemo @ Fujitsu-HO ~ :-( % systemd-resolve --status 20-05-18 12:54 Global LLMNR setting: no MulticastDNS setting: no DNSOverTLS setting: no DNSSEC setting: no DNSSEC supported: no DNSSEC NTA: 10.in-addr.arpa 16.172.in-addr.arpa 168.192.in-addr.arpa 17.172.in-addr.arpa 18.172.in-addr.arpa 19.172.in-addr.arpa 20.172.in-addr.arpa 21.172.in-addr.arpa 22.172.in-addr.arpa 23.172.in-addr.arpa 24.172.in-addr.arpa 25.172.in-addr.arpa 26.172.in-addr.arpa 27.172.in-addr.arpa 28.172.in-addr.arpa 29.172.in-addr.arpa 30.172.in-addr.arpa 31.172.in-addr.arpa corp d.f.ip6.arpa home internal intranet lan local private test Link 2 (enp0s25) Current Scopes: DNS DefaultRoute setting: yes LLMNR setting: yes MulticastDNS setting: no DNSOverTLS setting: no DNSSEC setting: no DNSSEC supported: no DNS Servers: 139.18.25.33 139.18.25.34 77.59.232.36 62.167.241.5 62.2.107.35 62.2.121.84 62.2.121.88 fd00::7eff:4dff:feaa:2528 2001:638:902:1::10 DNS Domain: ~. thiemo @ Fujitsu-HO ~ % host -v myworkspaceinet.post.ch 20-05-18 12:54 Trying "myworkspaceinet.post.ch" ;; connection timed out; no servers could be reached thiemo @ Fujitsu-HO ~ :-( % alias pong 20-05-18 12:55 pong='ping -c3' thiemo @ Fujitsu-HO ~ % pong 139.18.25.33 20-05-18 12:58 PING 139.18.25.33 (139.18.25.33) 56(84) bytes of data. 64 bytes from 139.18.25.33: icmp_seq=1 ttl=246 time=39.9 ms 64 bytes from 139.18.25.33: icmp_seq=2 ttl=246 time=39.0 ms 64 bytes from 139.18.25.33: icmp_seq=3 ttl=246 time=39.4 ms --- 139.18.25.33 ping statistics --- 3 packets transmitted, 3 received, 0% packet loss, time 2003ms rtt min/avg/max/mdev = 39.000/39.431/39.868/0.354 ms Kind regards Thiemo ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: network-manager 1.22.10-1ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30 Uname: Linux 5.4.0-29-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: KDE Date: Mon May 18 13:03:40 2020 InstallationDate: Installed on 2020-05-15 (3 days ago) InstallationMedia: Kubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) IpRoute: default via 192.168.178.1 dev enp0s25 proto dhcp metric 100 169.254.0.0/16 dev enp0s25 scope link metric 1000 192.168.178.0/24 dev enp0s25 proto kernel scope link src 192.168.178.33 metric 100 IwConfig: enp0s25 no wireless extensions. lono wireless extensions. RfKill: SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) nmcli-con: NAMEUUID TYPE TIMESTAMP TIMESTAMP-REALAUTOCONNECT AUTOCONNECT-PRIORITY READONLY DBUS-PATH ACTIVE DEVICE STATE ACTIVE-PATH SLAVE FILENAME Wired connection 1 3ce8a4c9-c011-3344-bbfd-9618a499a099 ethernet 1589799780 Mon May 18 13:03:00 2020 yes -100 no /org/freedesktop/NetworkManager/Settings/1 yes enp0s25 activated /org/freedesktop/NetworkManager/ActiveConnection/1 -- /etc/NetworkManager/system-connections/Wired connection 1.nmconnection nmcli-dev:
[Touch-packages] [Bug 1509717] Re: Wily LVM-RAID1 – md: personality for level 1 is not loaded
The regressions in bionic seem unrelated to me adding the raid1 module to the list of modules installed to the initramfs. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lvm2 in Ubuntu. https://bugs.launchpad.net/bugs/1509717 Title: Wily LVM-RAID1 – md: personality for level 1 is not loaded Status in linux package in Ubuntu: Invalid Status in lvm2 package in Ubuntu: Fix Released Status in linux source package in Bionic: Invalid Status in lvm2 source package in Bionic: Fix Committed Status in linux source package in Cosmic: Invalid Status in lvm2 source package in Cosmic: Won't Fix Status in linux source package in Disco: Invalid Status in lvm2 source package in Disco: Won't Fix Status in linux source package in Eoan: Invalid Status in lvm2 source package in Eoan: Fix Committed Status in lvm2 package in Debian: Incomplete Bug description: [Impact] system does not boot after converting lvm volume to raid1 w/o having mdadm installed. [Test case] 1. Install server with subiquity to LVM 2. Add second disk to it 3. Run pvcreate /dev/vdb 4. Run vgextend ubuntu-vg /dev/vdb 5. Run lvconvert -m1 --type raid1 ubuntu-vg/lv Reboot and check that it still boots. 6. Remove mdadm 7. Upgrade to lvm2 from proposed Reboot and check that it still boots. 8. Downgrade lvm2 to release Reboot and check that it fails to boot [Regression potential] Not really anything, we just add the raid1 module to initramfs, so it might be loaded during boot, and raid1 logical volumes might appear earlier. [Original bug report] After upgrading to Wily, raid1 LVs don't activate during the initrd phase. Since the root LV is also RAID1-mirrored, the system doesn't boot. I get the following message each time LVM tries to activate a raid1 LV: md: personality for level 1 is not loaded! Everything was fine with Vivid. I had to downgrade to Vivid kernel (3.19.0-30) to get my system to a usable state. I pretty much hope it to be a temporary workaround and I'll get the new 4.2.0 kernel work with Wily in days. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1509717/+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 1509717] Re: Wily LVM-RAID1 – md: personality for level 1 is not loaded
eoan verified. So, eoan is tougher. I installed it with subiquity and tried to follow the steps, but failed to convert to raid1, apparently, subiquity created the LV 1 PE larger than before or something, so it needed 1 free PE in the original PV to be able to add the raid1 metadata, which it did not have. Worked around this by extending the PV size after the install (after tryin to shrink the existing LV first, messing up the install, and reinstalling ...). With proposed lvm2 ubuntu6.1 it boots as wanted, downgrading to ubuntu6 in release breaks it again. ** Tags removed: verification-needed verification-needed-eoan ** Tags added: verification-done verification-done-eoan -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lvm2 in Ubuntu. https://bugs.launchpad.net/bugs/1509717 Title: Wily LVM-RAID1 – md: personality for level 1 is not loaded Status in linux package in Ubuntu: Invalid Status in lvm2 package in Ubuntu: Fix Released Status in linux source package in Bionic: Invalid Status in lvm2 source package in Bionic: Fix Committed Status in linux source package in Cosmic: Invalid Status in lvm2 source package in Cosmic: Won't Fix Status in linux source package in Disco: Invalid Status in lvm2 source package in Disco: Won't Fix Status in linux source package in Eoan: Invalid Status in lvm2 source package in Eoan: Fix Committed Status in lvm2 package in Debian: Incomplete Bug description: [Impact] system does not boot after converting lvm volume to raid1 w/o having mdadm installed. [Test case] 1. Install server with subiquity to LVM 2. Add second disk to it 3. Run pvcreate /dev/vdb 4. Run vgextend ubuntu-vg /dev/vdb 5. Run lvconvert -m1 --type raid1 ubuntu-vg/lv Reboot and check that it still boots. 6. Remove mdadm 7. Upgrade to lvm2 from proposed Reboot and check that it still boots. 8. Downgrade lvm2 to release Reboot and check that it fails to boot [Regression potential] Not really anything, we just add the raid1 module to initramfs, so it might be loaded during boot, and raid1 logical volumes might appear earlier. [Original bug report] After upgrading to Wily, raid1 LVs don't activate during the initrd phase. Since the root LV is also RAID1-mirrored, the system doesn't boot. I get the following message each time LVM tries to activate a raid1 LV: md: personality for level 1 is not loaded! Everything was fine with Vivid. I had to downgrade to Vivid kernel (3.19.0-30) to get my system to a usable state. I pretty much hope it to be a temporary workaround and I'll get the new 4.2.0 kernel work with Wily in days. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1509717/+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 1870359] Re: My machine as Wi-Fi Hotspot broken after upgrade to 20.04
1. I removed the network from the Wi-Fi setting and "Turn On Wi-Fi Hotspot..." is not grayed out. 2. I opened nm-connection-editor and click the +, then "Wi-Fi", then chose: - Mode: Hotspot - Device: wlp3s0 - No security 3. I connect with Ubuntu from another machine. There does appear to be a connection (WiFi settings has a check mark next to the network), but there is no internet and the icon remains a question mark. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1870359 Title: My machine as Wi-Fi Hotspot broken after upgrade to 20.04 Status in network-manager package in Ubuntu: Confirmed Bug description: I have a machine with a wired network connection and a wifi card. I've been using the machine as a wireless router and server in my house. I've attached a screenshot of the Wi-Fi network settings. It looks as expected. Upon updating to 20.04, none of my machines can use the connection. The linux machine will not connect. The windows machine will connect but will not have internet. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: network-manager 1.22.10-1ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.11-0ubuntu22 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Apr 2 15:47:02 2020 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2015-09-30 (1645 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) IpRoute: default via 192.168.0.1 dev eth0 proto static metric 100 169.254.0.0/16 dev eth0 scope link metric 1000 192.168.0.0/24 dev eth0 proto kernel scope link src 192.168.0.100 metric 100 SourcePackage: network-manager UpgradeStatus: Upgraded to focal on 2020-04-02 (0 days ago) WifiSyslog: mtime.conffile..etc.NetworkManager.NetworkManager.conf: 2018-01-13T14:45:42.987041 nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.22.10 connected started full enabled enabled enabled enabled enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1870359/+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 1870359] Re: My machine as Wi-Fi Hotspot broken after upgrade to 20.04
** Attachment added: "jrnlctl.txt" https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1870359/+attachment/5373391/+files/jrnlctl.txt -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1870359 Title: My machine as Wi-Fi Hotspot broken after upgrade to 20.04 Status in network-manager package in Ubuntu: Confirmed Bug description: I have a machine with a wired network connection and a wifi card. I've been using the machine as a wireless router and server in my house. I've attached a screenshot of the Wi-Fi network settings. It looks as expected. Upon updating to 20.04, none of my machines can use the connection. The linux machine will not connect. The windows machine will connect but will not have internet. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: network-manager 1.22.10-1ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.11-0ubuntu22 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Apr 2 15:47:02 2020 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2015-09-30 (1645 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) IpRoute: default via 192.168.0.1 dev eth0 proto static metric 100 169.254.0.0/16 dev eth0 scope link metric 1000 192.168.0.0/24 dev eth0 proto kernel scope link src 192.168.0.100 metric 100 SourcePackage: network-manager UpgradeStatus: Upgraded to focal on 2020-04-02 (0 days ago) WifiSyslog: mtime.conffile..etc.NetworkManager.NetworkManager.conf: 2018-01-13T14:45:42.987041 nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.22.10 connected started full enabled enabled enabled enabled enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1870359/+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 1509717] Re: Wily LVM-RAID1 – md: personality for level 1 is not loaded
** Tags added: id-5d0ba914f340e31a8e9f2cf1 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lvm2 in Ubuntu. https://bugs.launchpad.net/bugs/1509717 Title: Wily LVM-RAID1 – md: personality for level 1 is not loaded Status in linux package in Ubuntu: Invalid Status in lvm2 package in Ubuntu: Fix Released Status in linux source package in Bionic: Invalid Status in lvm2 source package in Bionic: Fix Committed Status in linux source package in Cosmic: Invalid Status in lvm2 source package in Cosmic: Won't Fix Status in linux source package in Disco: Invalid Status in lvm2 source package in Disco: Won't Fix Status in linux source package in Eoan: Invalid Status in lvm2 source package in Eoan: Fix Committed Status in lvm2 package in Debian: Incomplete Bug description: [Impact] system does not boot after converting lvm volume to raid1 w/o having mdadm installed. [Test case] 1. Install server with subiquity to LVM 2. Add second disk to it 3. Run pvcreate /dev/vdb 4. Run vgextend ubuntu-vg /dev/vdb 5. Run lvconvert -m1 --type raid1 ubuntu-vg/lv Reboot and check that it still boots. 6. Remove mdadm 7. Upgrade to lvm2 from proposed Reboot and check that it still boots. 8. Downgrade lvm2 to release Reboot and check that it fails to boot [Regression potential] Not really anything, we just add the raid1 module to initramfs, so it might be loaded during boot, and raid1 logical volumes might appear earlier. [Original bug report] After upgrading to Wily, raid1 LVs don't activate during the initrd phase. Since the root LV is also RAID1-mirrored, the system doesn't boot. I get the following message each time LVM tries to activate a raid1 LV: md: personality for level 1 is not loaded! Everything was fine with Vivid. I had to downgrade to Vivid kernel (3.19.0-30) to get my system to a usable state. I pretty much hope it to be a temporary workaround and I'll get the new 4.2.0 kernel work with Wily in days. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1509717/+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 1876018] Re: 40-vm-hotadd.rules attempts to set non-existent sysfs parameters
** Tags added: id-5eac701c52dbda63e8c9b00c
--
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/1876018
Title:
40-vm-hotadd.rules attempts to set non-existent sysfs parameters
Status in systemd package in Ubuntu:
In Progress
Status in systemd source package in Focal:
New
Bug description:
In focal, udev's 40-vm-hotadd.rules (from debian/extra/rules-ubuntu)
tries to write to invalid (as of 5.4.0-1010-azure) sysfs nodes
resulting in warnings such as:
Apr 29 22:36:46 focal01 systemd-udevd[266]: memory7:
/usr/lib/udev/rules.d/40-vm-hotadd.rules:9 Failed to write
ATTR{/sys/devices/system/memory/memory7/state}, ignoring: Invalid
argument
Perhaps 40-vm-hotadd.rules needs to be updated for 5.4 semantics,
removed, or something else. This behavior is present on systems
upgraded from 18.04 (via d-r-u) as well as new focal systems, upon
first reboot of the VM.
udev: 245.4-4ubuntu3
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1876018/+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 1877895] Re: package udev 245.4-4ubuntu3 failed to install/upgrade: o subprocesso instalado, do pacote udev, o script post-installation retornou erro do status de saída 1
I can't download the attachment, but it looks quite odd already from the original name. Please try reinstalling udev. -- 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/1877895 Title: package udev 245.4-4ubuntu3 failed to install/upgrade: o subprocesso instalado, do pacote udev, o script post-installation retornou erro do status de saída 1 Status in systemd package in Ubuntu: Incomplete Bug description: after updating from 18.04 to 20.04, appears errors constantly ProblemType: Package DistroRelease: Ubuntu 20.04 Package: udev 245.4-4ubuntu3 ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30 Uname: Linux 5.4.0-29-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CustomUdevRuleFiles: 70-snap.spotify.rules 70-snap.core.rules Date: Sat May 9 10:24:26 2020 ErrorMessage: o subprocesso instalado, do pacote udev, o script post-installation retornou erro do status de saída 1 InstallationDate: Installed on 2020-05-09 (1 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) MachineType: Sony Corporation SVE15125CBW ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-29-generic root=UUID=53223737-2091-4487-a0b3-a2b80db164ad ro quiet splash Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: /usr/bin/python2.7, Python 2.7.18rc1, python-minimal, 2.7.15~rc1-1 RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.2 SourcePackage: systemd Title: package udev 245.4-4ubuntu3 failed to install/upgrade: o subprocesso instalado, do pacote udev, o script post-installation retornou erro do status de saída 1 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/14/2012 dmi.bios.vendor: Insyde Corp. dmi.bios.version: R0170D5 dmi.board.asset.tag: N/A dmi.board.name: VAIO dmi.board.vendor: Sony Corporation dmi.board.version: N/A dmi.chassis.asset.tag: N/A dmi.chassis.type: 10 dmi.chassis.vendor: Sony Corporation dmi.chassis.version: N/A dmi.modalias: dmi:bvnInsydeCorp.:bvrR0170D5:bd11/14/2012:svnSonyCorporation:pnSVE15125CBW:pvrC800EQPLK:rvnSonyCorporation:rnVAIO:rvrN/A:cvnSonyCorporation:ct10:cvrN/A: dmi.product.family: VAIO dmi.product.name: SVE15125CBW dmi.product.sku: 54508549 dmi.product.version: C800EQPLK dmi.sys.vendor: Sony Corporation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1877895/+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 1879282] Re: Workspace shows windows that is not on the current workspace
** Package changed: ubuntu => xorg (Ubuntu) -- 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/1879282 Title: Workspace shows windows that is not on the current workspace Status in xorg package in Ubuntu: New Bug description: If I have two workspaces and have for example firefox on both workspaces, then the second workspace will show the firefox windows that is on the first workspace. I can not controll this window, its just a piece of the background. I get this problem 100% of the time. The way I get it is by being on my second workspace, howering my pointer over the firefox on my topbar, go through the windows of the windows open for firefox, which makes my screen jump to the first window when i hower over the firefox window that is open on the first workspace, to indicate where it is located. Then when i click on the firefox window that is on the second workspace, the window from the first workspace is "stuck" as a wallpaper. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30 Uname: Linux 5.4.0-29-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Mon May 18 10:59:15 2020 DistUpgraded: 2020-04-26 19:27:56,468 DEBUG icon theme changed, re-reading DistroCodename: focal DistroVariant: ubuntu GraphicsCard: Intel Corporation HD Graphics 620 [8086:5916] (rev 02) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. HD Graphics 620 [1043:1740] InstallationDate: Installed on 2020-04-17 (30 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 04f3:0903 Elan Microelectronics Corp. ELAN:Fingerprint Bus 001 Device 003: ID 8087:0a2b Intel Corp. Bus 001 Device 002: ID 0bda:58e4 Realtek Semiconductor Corp. USB2.0 HD UVC WebCam Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: ASUSTeK COMPUTER INC. UX430UA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-29-generic root=UUID=dc6ec013-e29e-4a5e-8dd0-17ae3cf639fc ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to focal on 2020-04-26 (21 days ago) dmi.bios.date: 11/14/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: UX430UA.304 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX430UA dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrUX430UA.304:bd11/14/2017:svnASUSTeKCOMPUTERINC.:pnUX430UA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX430UA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: UX dmi.product.name: UX430UA dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. 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 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 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1879282/+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 1879282] [NEW] Workspace shows windows that is not on the current workspace
You have been subscribed to a public bug: If I have two workspaces and have for example firefox on both workspaces, then the second workspace will show the firefox windows that is on the first workspace. I can not controll this window, its just a piece of the background. I get this problem 100% of the time. The way I get it is by being on my second workspace, howering my pointer over the firefox on my topbar, go through the windows of the windows open for firefox, which makes my screen jump to the first window when i hower over the firefox window that is open on the first workspace, to indicate where it is located. Then when i click on the firefox window that is on the second workspace, the window from the first workspace is "stuck" as a wallpaper. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30 Uname: Linux 5.4.0-29-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Mon May 18 10:59:15 2020 DistUpgraded: 2020-04-26 19:27:56,468 DEBUG icon theme changed, re-reading DistroCodename: focal DistroVariant: ubuntu GraphicsCard: Intel Corporation HD Graphics 620 [8086:5916] (rev 02) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. HD Graphics 620 [1043:1740] InstallationDate: Installed on 2020-04-17 (30 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 04f3:0903 Elan Microelectronics Corp. ELAN:Fingerprint Bus 001 Device 003: ID 8087:0a2b Intel Corp. Bus 001 Device 002: ID 0bda:58e4 Realtek Semiconductor Corp. USB2.0 HD UVC WebCam Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: ASUSTeK COMPUTER INC. UX430UA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-29-generic root=UUID=dc6ec013-e29e-4a5e-8dd0-17ae3cf639fc ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to focal on 2020-04-26 (21 days ago) dmi.bios.date: 11/14/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: UX430UA.304 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX430UA dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrUX430UA.304:bd11/14/2017:svnASUSTeKCOMPUTERINC.:pnUX430UA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX430UA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: UX dmi.product.name: UX430UA dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. 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 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 focal ubuntu -- Workspace shows windows that is not on the current workspace https://bugs.launchpad.net/bugs/1879282 You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg 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 1872824] Re: Can't upgrade console-setup-linux (1.194ubuntu3) over (1.108ubuntu15.5), trying to overwrite '/lib/systemd/system/console-setup.service', which is also in package ke
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: console-setup (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to console-setup in Ubuntu. https://bugs.launchpad.net/bugs/1872824 Title: Can't upgrade console-setup-linux (1.194ubuntu3) over (1.108ubuntu15.5), trying to overwrite '/lib/systemd/system/console- setup.service', which is also in package keyboard-configuration 1.108ubuntu15.5 Status in console-setup package in Ubuntu: Confirmed Bug description: Upgrade path from 16.04 to 20.04 fails. console-setup-linux_1.194ubuntu3_all.deb tries to overwrite '/lib/systemd/system/console-setup.service', which is also in package keyboard-configuration 1.108ubuntu15.5. I have reproduced this bug on bare metal and WSL. Log: Unpacking console-setup-linux (1.194ubuntu3) over (1.108ubuntu15.5) ... dpkg: error processing archive /var/cache/apt/archives/console-setup-linux_1.194ubuntu3_all.deb (--unpack): trying to overwrite '/lib/systemd/system/console-setup.service', which is also in package keyboard-configuration 1.108ubuntu15.5 dpkg-deb: error: subprocess paste was killed by signal (Broken pipe) Preparing to unpack .../keyboard-configuration_1.194ubuntu3_all.deb ... Unpacking keyboard-configuration (1.194ubuntu3) over (1.108ubuntu15.5) ... Preparing to unpack .../busybox-initramfs_1%3a1.30.1-4ubuntu6_amd64.deb ... Unpacking busybox-initramfs (1:1.30.1-4ubuntu6) over (1:1.22.0-15ubuntu1.4) ... Preparing to unpack .../initramfs-tools-bin_0.136ubuntu6_amd64.deb ... Unpacking initramfs-tools-bin (0.136ubuntu6) over (0.122ubuntu8.16) ... Preparing to unpack .../cpio_2.13+dfsg-2_amd64.deb ... Unpacking cpio (2.13+dfsg-2) over (2.11+dfsg-5ubuntu1.1) ... Preparing to unpack .../liblz4-1_1.9.2-2_amd64.deb ... Unpacking liblz4-1:amd64 (1.9.2-2) over (0.0~r131-2ubuntu2) ... Processing triggers for libc-bin (2.31-0ubuntu7) ... Processing triggers for ureadahead (0.100.0-19.1) ... Processing triggers for systemd (229-4ubuntu21.27) ... Processing triggers for man-db (2.7.5-1) ... Errors were encountered while processing: /var/cache/apt/archives/console-setup-linux_1.194ubuntu3_all.deb E: Sub-process /usr/bin/dpkg returned an error code (1) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/console-setup/+bug/1872824/+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 1879311] [NEW] [There is no sound on the headset, Aspire E1-572, Realtek ALC282, Black Headphone Out, Left] Playback problem
Public bug reported: When I select in the settings what sound comes out of the headset. He continues to go through the notebook's internal speaker. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30 Uname: Linux 5.4.0-29-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: merencio 1779 F pulseaudio /dev/snd/controlC2: merencio 1779 F pulseaudio /dev/snd/controlC0: merencio 1779 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Mon May 18 08:06:49 2020 InstallationDate: Installed on 2020-04-18 (30 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_Jack: Black Headphone Out, Left Symptom_Type: None of the above Title: [Aspire E1-572, Realtek ALC282, Black Headphone Out, Left] Playback problem UpgradeStatus: Upgraded to focal on 2020-05-17 (0 days ago) dmi.bios.date: 11/21/2013 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V2.13 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: EA50_HW dmi.board.vendor: Acer dmi.board.version: V2.13 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsydeCorp.:bvrV2.13:bd11/21/2013:svnAcer:pnAspireE1-572:pvrV2.13:rvnAcer:rnEA50_HW:rvrV2.13:cvnAcer:ct10:cvrChassisVersion: dmi.product.family: SharkBay System dmi.product.name: Aspire E1-572 dmi.product.sku: Aspire E1-572_0775_V2.13 dmi.product.version: V2.13 dmi.sys.vendor: Acer mtime.conffile..etc.modprobe.d.alsa-base.conf: 2020-05-18T07:17:21.090034 ** Affects: alsa-driver (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1879311 Title: [There is no sound on the headset, Aspire E1-572, Realtek ALC282, Black Headphone Out, Left] Playback problem Status in alsa-driver package in Ubuntu: New Bug description: When I select in the settings what sound comes out of the headset. He continues to go through the notebook's internal speaker. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30 Uname: Linux 5.4.0-29-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: merencio 1779 F pulseaudio /dev/snd/controlC2: merencio 1779 F pulseaudio /dev/snd/controlC0: merencio 1779 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Mon May 18 08:06:49 2020 InstallationDate: Installed on 2020-04-18 (30 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_Jack: Black Headphone Out, Left Symptom_Type: None of the above Title: [Aspire E1-572, Realtek ALC282, Black Headphone Out, Left] Playback problem UpgradeStatus: Upgraded to focal on 2020-05-17 (0 days ago) dmi.bios.date: 11/21/2013 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V2.13 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: EA50_HW dmi.board.vendor: Acer dmi.board.version: V2.13 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsydeCorp.:bvrV2.13:bd11/21/2013:svnAcer:pnAspireE1-572:pvrV2.13:rvnAcer:rnEA50_HW:rvrV2.13:cvnAcer:ct10:cvrChassisVersion: dmi.product.family: SharkBay System dmi.product.name: Aspire E1-572 dmi.product.sku: Aspire E1-572_0775_V2.13 dmi.product.version: V2.13 dmi.sys.vendor: Acer mtime.conffile..etc.modprobe.d.alsa-base.conf: 2020-05-18T07:17:21.090034 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1879311/+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 1876018] Re: 40-vm-hotadd.rules attempts to set non-existent sysfs parameters
@ddstreet, thanks, the fix works and I'll include it in the next upload
to Groovy, in the next days.
** Also affects: systemd (Ubuntu Focal)
Importance: Undecided
Status: New
** Changed in: systemd (Ubuntu)
Status: New => In Progress
--
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/1876018
Title:
40-vm-hotadd.rules attempts to set non-existent sysfs parameters
Status in systemd package in Ubuntu:
In Progress
Status in systemd source package in Focal:
New
Bug description:
In focal, udev's 40-vm-hotadd.rules (from debian/extra/rules-ubuntu)
tries to write to invalid (as of 5.4.0-1010-azure) sysfs nodes
resulting in warnings such as:
Apr 29 22:36:46 focal01 systemd-udevd[266]: memory7:
/usr/lib/udev/rules.d/40-vm-hotadd.rules:9 Failed to write
ATTR{/sys/devices/system/memory/memory7/state}, ignoring: Invalid
argument
Perhaps 40-vm-hotadd.rules needs to be updated for 5.4 semantics,
removed, or something else. This behavior is present on systems
upgraded from 18.04 (via d-r-u) as well as new focal systems, upon
first reboot of the VM.
udev: 245.4-4ubuntu3
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1876018/+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 1870442] Missing required logs.
This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window: apport-collect 1870442 and then change the status of the bug to 'Confirmed'. If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'. This change has been made by an automated script, maintained by the Ubuntu Kernel Team. ** Changed in: linux (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1870442 Title: Laptop drops connection to the Internet after reboot, forcing me to reset by turning Wi-Fi off and then back on. Status in linux package in Ubuntu: Incomplete Status in network-manager package in Ubuntu: Incomplete Bug description: When I was trying to connect to the network after rebooting the computer, and I disabled verification before the reboot, the laptop connected, but then, even though no other computers had this problem, the speed of the wi-fi shut down, and then the connection with the router dropped. All this until I turned Airplane Mode on and Wi-Fi on my PC for a brief second before disabling airplane mode and reenabling Wi-Fi. Ubuntu 18.04.4 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: network-manager 1.10.6-2ubuntu1.4 ProcVersionSignature: Ubuntu 5.3.0-45.37~18.04.1-generic 5.3.18 Uname: Linux 5.3.0-45-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.14 Architecture: amd64 Date: Thu Apr 2 18:25:30 2020 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2020-04-01 (0 days ago) InstallationMedia: Ubuntu 18.04.4 LTS "Bionic Beaver" - Release amd64 (20200203.1) IpRoute: default via 192.168.1.1 dev wlp2s0 proto dhcp metric 600 169.254.0.0/16 dev wlp2s0 scope link metric 1000 192.168.1.0/24 dev wlp2s0 proto kernel scope link src 192.168.1.39 metric 600 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) nmcli-con: NAMEUUID TYPE TIMESTAMP TIMESTAMP-REAL AUTOCONNECT AUTOCONNECT-PRIORITY READONLY DBUS-PATH ACTIVE DEVICE STATE ACTIVE-PATH SLAVE NETGEAR18 6fbfa44b-461e-4067-b37a-26f63bc54f88 wifi 1585866147 Thu 02 Apr 2020 06:22:27 PM EDT yes 0 no/org/freedesktop/NetworkManager/Settings/1 yes wlp2s0 activated /org/freedesktop/NetworkManager/ActiveConnection/1 -- Wired connection 1 0c4f5994-e9fb-3218-9aa5-d46003ebcd5a ethernet 1585865851 Thu 02 Apr 2020 06:17:31 PM EDT yes 4294966297 no/org/freedesktop/NetworkManager/Settings/2 no -- -- -- -- nmcli-dev: DEVICE TYPE STATEDBUS-PATH CONNECTION CON-UUID CON-PATH wlp2s0 wifi connected/org/freedesktop/NetworkManager/Devices/3 NETGEAR18 6fbfa44b-461e-4067-b37a-26f63bc54f88 /org/freedesktop/NetworkManager/ActiveConnection/1 enp1s0 ethernet unavailable /org/freedesktop/NetworkManager/Devices/2 -- ---- lo loopback unmanaged/org/freedesktop/NetworkManager/Devices/1 -- ---- nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.10.6 connected started full enabled enabled enabled enabled enabled --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 CasperVersion: 1.394.3 DistroRelease: Ubuntu 18.04 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback IpRoute: default via 192.168.1.1 dev wlp2s0 proto dhcp metric 600 169.254.0.0/16 dev wlp2s0 scope link metric 1000 192.168.1.0/24 dev wlp2s0 proto kernel scope link src 192.168.1.39 metric 600 LiveMediaBuild: Ubuntu 18.04.4 LTS "Bionic Beaver" - Release amd64 (20200203.1) NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true Package:
[Touch-packages] [Bug 1876125] Re: SRU the current 3.36.2 stable update
Using 3.36.2-0ubuntu1 calendar integration in the desktop, the standalone application and the evolution components still work correctly, marking as verified The libreoffice test is flackyness and worked after a retry ** Tags removed: verification-needed verification-needed-focal ** Tags added: verification-done verification-done-focal -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to evolution-data-server in Ubuntu. https://bugs.launchpad.net/bugs/1876125 Title: SRU the current 3.36.2 stable update Status in evolution-data-server package in Ubuntu: Fix Released Status in evolution-data-server source package in Focal: Fix Committed Bug description: * Impact That's the current GNOME stable update, including some fixes and translation updates https://gitlab.gnome.org/GNOME/evolution-data-server/-/blob/gnome-3-36/NEWS * Test case The update is part of GNOME stable updates https://wiki.ubuntu.com/StableReleaseUpdates/GNOME Check that the calendar integration in GNOME and gnome-calendar is working, also test evolution with an email account. * Regression potential There is no specific change or feature to test in the upgrade To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evolution-data-server/+bug/1876125/+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 1877895] Re: package udev 245.4-4ubuntu3 failed to install/upgrade: o subprocesso instalado, do pacote udev, o script post-installation retornou erro do status de saída 1
Please attach output of: cat /lib/systemd/system/systemd-udevd.service Running the following command may fix the issue: sudo apt install --reinstall udev ** Changed in: systemd (Ubuntu) Status: New => Incomplete -- 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/1877895 Title: package udev 245.4-4ubuntu3 failed to install/upgrade: o subprocesso instalado, do pacote udev, o script post-installation retornou erro do status de saída 1 Status in systemd package in Ubuntu: Incomplete Bug description: after updating from 18.04 to 20.04, appears errors constantly ProblemType: Package DistroRelease: Ubuntu 20.04 Package: udev 245.4-4ubuntu3 ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30 Uname: Linux 5.4.0-29-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CustomUdevRuleFiles: 70-snap.spotify.rules 70-snap.core.rules Date: Sat May 9 10:24:26 2020 ErrorMessage: o subprocesso instalado, do pacote udev, o script post-installation retornou erro do status de saída 1 InstallationDate: Installed on 2020-05-09 (1 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) MachineType: Sony Corporation SVE15125CBW ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-29-generic root=UUID=53223737-2091-4487-a0b3-a2b80db164ad ro quiet splash Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: /usr/bin/python2.7, Python 2.7.18rc1, python-minimal, 2.7.15~rc1-1 RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.2 SourcePackage: systemd Title: package udev 245.4-4ubuntu3 failed to install/upgrade: o subprocesso instalado, do pacote udev, o script post-installation retornou erro do status de saída 1 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/14/2012 dmi.bios.vendor: Insyde Corp. dmi.bios.version: R0170D5 dmi.board.asset.tag: N/A dmi.board.name: VAIO dmi.board.vendor: Sony Corporation dmi.board.version: N/A dmi.chassis.asset.tag: N/A dmi.chassis.type: 10 dmi.chassis.vendor: Sony Corporation dmi.chassis.version: N/A dmi.modalias: dmi:bvnInsydeCorp.:bvrR0170D5:bd11/14/2012:svnSonyCorporation:pnSVE15125CBW:pvrC800EQPLK:rvnSonyCorporation:rnVAIO:rvrN/A:cvnSonyCorporation:ct10:cvrN/A: dmi.product.family: VAIO dmi.product.name: SVE15125CBW dmi.product.sku: 54508549 dmi.product.version: C800EQPLK dmi.sys.vendor: Sony Corporation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1877895/+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 1875605] Re: SRU the current 0.20.3 stable update
The gvfs regression is a known flaky test and cleared after retry The new 0.20.3-0ubuntu1 works fine, including ssh and gpg keys handling and the password manager software, marked as verified ** Tags removed: verification-needed verification-needed-focal ** Tags added: verification-done verification-done-focal -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libsecret in Ubuntu. https://bugs.launchpad.net/bugs/1875605 Title: SRU the current 0.20.3 stable update Status in libsecret package in Ubuntu: Fix Released Status in libsecret source package in Focal: Fix Committed Bug description: * Impact That's the current GNOME stable update, including some fixes https://gitlab.gnome.org/GNOME/libsecret/-/blob/master/NEWS * Test case The update is part of GNOME stable updates https://wiki.ubuntu.com/StableReleaseUpdates/GNOME Check that using passwords in GNOME applications or gpg/ssh keys still work correctly * Regression potential There is a segfault fix for flapak portals, testing that usecase would be useful To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libsecret/+bug/1875605/+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 1869940] Missing required logs.
This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window: apport-collect 1869940 and then change the status of the bug to 'Confirmed'. If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'. This change has been made by an automated script, maintained by the Ubuntu Kernel Team. ** Changed in: linux (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1869940 Title: No networks available/visible after suspend Status in linux package in Ubuntu: Incomplete Status in network-manager package in Ubuntu: New Bug description: WiFI network disconnected and no networks visible after resume from suspend. Had to reboot the machine to get networking (WiFI) back up and running. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: network-manager 1.22.10-1ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 ApportVersion: 2.20.11-0ubuntu21 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Mar 31 21:18:43 2020 InstallationDate: Installed on 2020-03-31 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200330) IpRoute: default via 192.168.1.1 dev wlp59s0 proto dhcp metric 600 169.254.0.0/16 dev wlp59s0 scope link metric 1000 192.168.1.0/24 dev wlp59s0 proto kernel scope link src 192.168.1.30 metric 600 SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) nmcli-con: NAMEUUID TYPE TIMESTAMP TIMESTAMP-REALAUTOCONNECT AUTOCONNECT-PRIORITY READONLY DBUS-PATH ACTIVE DEVICE STATE ACTIVE-PATH SLAVE FILENAME DORIAN 2c3f821d-0865-4747-974a-2f861ee0dc38 wifi 1585682245 tis 31 mar 2020 21:17:25 yes 0 no /org/freedesktop/NetworkManager/Settings/1 yes wlp59s0 activated /org/freedesktop/NetworkManager/ActiveConnection/1 -- /etc/NetworkManager/system-connections/DORIAN.nmconnection nmcli-dev: DEVICE TYPE STATE IP4-CONNECTIVITY IP6-CONNECTIVITY DBUS-PATH CONNECTION CON-UUID CON-PATH wlp59s0 wifi connected full limited /org/freedesktop/NetworkManager/Devices/2 DORIAN 2c3f821d-0865-4747-974a-2f861ee0dc38 /org/freedesktop/NetworkManager/ActiveConnection/1 p2p-dev-wlp59s0 wifi-p2p disconnected none none /org/freedesktop/NetworkManager/Devices/3 -- -- -- lo loopback unmanaged unknown unknown /org/freedesktop/NetworkManager/Devices/1 -- -- -- nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.22.10 connected started full enabled enabled enabled enabled enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1869940/+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 1870442] Re: Laptop drops connection to the Internet after reboot, forcing me to reset by turning Wi-Fi off and then back on.
** Also affects: linux (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1870442 Title: Laptop drops connection to the Internet after reboot, forcing me to reset by turning Wi-Fi off and then back on. Status in linux package in Ubuntu: Incomplete Status in network-manager package in Ubuntu: Incomplete Bug description: When I was trying to connect to the network after rebooting the computer, and I disabled verification before the reboot, the laptop connected, but then, even though no other computers had this problem, the speed of the wi-fi shut down, and then the connection with the router dropped. All this until I turned Airplane Mode on and Wi-Fi on my PC for a brief second before disabling airplane mode and reenabling Wi-Fi. Ubuntu 18.04.4 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: network-manager 1.10.6-2ubuntu1.4 ProcVersionSignature: Ubuntu 5.3.0-45.37~18.04.1-generic 5.3.18 Uname: Linux 5.3.0-45-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.14 Architecture: amd64 Date: Thu Apr 2 18:25:30 2020 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2020-04-01 (0 days ago) InstallationMedia: Ubuntu 18.04.4 LTS "Bionic Beaver" - Release amd64 (20200203.1) IpRoute: default via 192.168.1.1 dev wlp2s0 proto dhcp metric 600 169.254.0.0/16 dev wlp2s0 scope link metric 1000 192.168.1.0/24 dev wlp2s0 proto kernel scope link src 192.168.1.39 metric 600 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) nmcli-con: NAMEUUID TYPE TIMESTAMP TIMESTAMP-REAL AUTOCONNECT AUTOCONNECT-PRIORITY READONLY DBUS-PATH ACTIVE DEVICE STATE ACTIVE-PATH SLAVE NETGEAR18 6fbfa44b-461e-4067-b37a-26f63bc54f88 wifi 1585866147 Thu 02 Apr 2020 06:22:27 PM EDT yes 0 no/org/freedesktop/NetworkManager/Settings/1 yes wlp2s0 activated /org/freedesktop/NetworkManager/ActiveConnection/1 -- Wired connection 1 0c4f5994-e9fb-3218-9aa5-d46003ebcd5a ethernet 1585865851 Thu 02 Apr 2020 06:17:31 PM EDT yes 4294966297 no/org/freedesktop/NetworkManager/Settings/2 no -- -- -- -- nmcli-dev: DEVICE TYPE STATEDBUS-PATH CONNECTION CON-UUID CON-PATH wlp2s0 wifi connected/org/freedesktop/NetworkManager/Devices/3 NETGEAR18 6fbfa44b-461e-4067-b37a-26f63bc54f88 /org/freedesktop/NetworkManager/ActiveConnection/1 enp1s0 ethernet unavailable /org/freedesktop/NetworkManager/Devices/2 -- ---- lo loopback unmanaged/org/freedesktop/NetworkManager/Devices/1 -- ---- nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.10.6 connected started full enabled enabled enabled enabled enabled --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 CasperVersion: 1.394.3 DistroRelease: Ubuntu 18.04 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback IpRoute: default via 192.168.1.1 dev wlp2s0 proto dhcp metric 600 169.254.0.0/16 dev wlp2s0 scope link metric 1000 192.168.1.0/24 dev wlp2s0 proto kernel scope link src 192.168.1.39 metric 600 LiveMediaBuild: Ubuntu 18.04.4 LTS "Bionic Beaver" - Release amd64 (20200203.1) NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true Package: network-manager 1.10.6-2ubuntu1.2 PackageArchitecture: amd64 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=C.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 5.3.0-28.30~18.04.1-generic 5.3.13 Tags: bionic Uname: Linux 5.3.0-28-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True nmcli-con: NAMEUUID TYPE TIMESTAMP TIMESTAMP-REALAUTOCONNECT
[Touch-packages] [Bug 1869940] Re: No networks available/visible after suspend
Please reproduce the issue then attach dmesg. ** Also affects: linux (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1869940 Title: No networks available/visible after suspend Status in linux package in Ubuntu: Incomplete Status in network-manager package in Ubuntu: New Bug description: WiFI network disconnected and no networks visible after resume from suspend. Had to reboot the machine to get networking (WiFI) back up and running. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: network-manager 1.22.10-1ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 ApportVersion: 2.20.11-0ubuntu21 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Mar 31 21:18:43 2020 InstallationDate: Installed on 2020-03-31 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200330) IpRoute: default via 192.168.1.1 dev wlp59s0 proto dhcp metric 600 169.254.0.0/16 dev wlp59s0 scope link metric 1000 192.168.1.0/24 dev wlp59s0 proto kernel scope link src 192.168.1.30 metric 600 SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) nmcli-con: NAMEUUID TYPE TIMESTAMP TIMESTAMP-REALAUTOCONNECT AUTOCONNECT-PRIORITY READONLY DBUS-PATH ACTIVE DEVICE STATE ACTIVE-PATH SLAVE FILENAME DORIAN 2c3f821d-0865-4747-974a-2f861ee0dc38 wifi 1585682245 tis 31 mar 2020 21:17:25 yes 0 no /org/freedesktop/NetworkManager/Settings/1 yes wlp59s0 activated /org/freedesktop/NetworkManager/ActiveConnection/1 -- /etc/NetworkManager/system-connections/DORIAN.nmconnection nmcli-dev: DEVICE TYPE STATE IP4-CONNECTIVITY IP6-CONNECTIVITY DBUS-PATH CONNECTION CON-UUID CON-PATH wlp59s0 wifi connected full limited /org/freedesktop/NetworkManager/Devices/2 DORIAN 2c3f821d-0865-4747-974a-2f861ee0dc38 /org/freedesktop/NetworkManager/ActiveConnection/1 p2p-dev-wlp59s0 wifi-p2p disconnected none none /org/freedesktop/NetworkManager/Devices/3 -- -- -- lo loopback unmanaged unknown unknown /org/freedesktop/NetworkManager/Devices/1 -- -- -- nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.22.10 connected started full enabled enabled enabled enabled enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1869940/+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 1859308] Re: software-properties-gtk erroneously reports that certain Intel wireless adapter cards are not working
same here on lenovo x1 carbon u20.04 upgraded from 18.04: ubuntu-drivers devices == /sys/devices/pci:00/:00:1c.2/:04:00.0 == modalias : pci:v8086d24FDsv8086sd1130bc02sc80i00 vendor : Intel Corporation model: Wireless 8265 / 8275 (Dual Band Wireless-AC 8265) manual_install: True driver : backport-iwlwifi-dkms - distro free ubuntu-drivers install No drivers found for installation. -- 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/1859308 Title: software-properties-gtk erroneously reports that certain Intel wireless adapter cards are not working Status in software-properties package in Ubuntu: Confirmed Bug description: On Ubuntu 20.04 (development branch), as of today, Additional Drivers (software-properties-gtk 0.98.6) reports that the device "Intel Corporation: Wireless-AC 9260" is not working, and suggests using a manually installed driver (cf. screenshot). However the device is working correctly: * lsmod | grep iwlwifi, lspci -v, lshw, dmesg | grep iwlwifi all show that its driver iwlwifi is in use * ls /lib/firmware/*9260* show that the appropriate firmware files are present And I am indeed writing this bug report connected to an ac (5 GHz) wifi network, where I can verify a ~130-160 Mbps download speed, so software-properties-gtk shouldn't report the device as not working and suggest manually installing a driver. Not sure why it says so? EDIT: bug confirmed as affecting the following Intel wireless adapter cards, and assumedly more to come: Intel Wi-Fi 6 AX200 Intel Dual Band Wireless-AC 3165 Intel Dual Band Wireless-AC 7260 Intel Dual Band Wireless-AC 8260 Intel Wireless-AC 9260 Also for reference here are the specs of Intel adapter cards: ark.intel.com/content/www/us/en/ark.html#@WirelessNetworking ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: software-properties-gtk 0.98.6 ProcVersionSignature: Ubuntu 5.4.0-9.12-generic 5.4.3 Uname: Linux 5.4.0-9-generic x86_64 ApportVersion: 2.20.11-0ubuntu15 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sun Jan 12 00:53:43 2020 ExecutablePath: /usr/bin/software-properties-gtk InstallationDate: Installed on 2019-12-29 (13 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20191226) InterpreterPath: /usr/bin/python3.7 PackageArchitecture: all Python3Details: /usr/bin/python3.7, Python 3.7.6, python3-minimal, 3.7.5-1ubuntu1 PythonDetails: /usr/bin/python2.7, Python 2.7.17, python-minimal, 2.7.17-1 SourcePackage: software-properties UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1859308/+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 1878738] Re: program abort by "lh_table_new: calloc failed"
Seems to affect all software which uses this library. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to json-c in Ubuntu. https://bugs.launchpad.net/bugs/1878738 Title: program abort by "lh_table_new: calloc failed" Status in json-c package in Ubuntu: Confirmed Bug description: I wrote small sample program which abort by lh_table_new calloc failed. see this. https://gist.github.com/735eec6fd0869df1facb08da5baa402c To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/json-c/+bug/1878738/+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 1872863] Re: QEMU/KVM display is garbled when booting from kernel EFI stub due to missing bochs-drm module
This bug was fixed in the package linux - 4.15.0-101.102
---
linux (4.15.0-101.102) bionic; urgency=medium
* bionic/linux: 4.15.0-101.102 -proposed tracker (LP: #1877262)
* 4.15.0-100.101 breaks userspace builds due to a bug in the headers
/usr/include/linux/swab.h of linux-libc-dev (LP: #1877123)
- include/uapi/linux/swab.h: fix userspace breakage, use __BITS_PER_LONG for
swap
* bionic snapdragon 4.15 snap failed Certification testing (LP: #1877657)
- Revert "drm/msm: Use the correct dma_sync calls in msm_gem"
- Revert "drm/msm: stop abusing dma_map/unmap for cache"
linux (4.15.0-100.101) bionic; urgency=medium
* bionic/linux: 4.15.0-100.101 -proposed tracker (LP: #1875878)
* built-using constraints preventing uploads (LP: #1875601)
- temporarily drop Built-Using data
* Add debian/rules targets to compile/run kernel selftests (LP: #1874286)
- [Packaging] add support to compile/run selftests
* getitimer returns it_value=0 erroneously (LP: #1349028)
- [Config] CONTEXT_TRACKING_FORCE policy should be unset
* QEMU/KVM display is garbled when booting from kernel EFI stub due to missing
bochs-drm module (LP: #1872863)
- [Config] Enable CONFIG_DRM_BOCHS as module for all archs
* Backport MPLS patches from 5.3 to 4.15 (LP: #1851446)
- net/mlx5e: Report netdevice MPLS features
- net: vlan: Inherit MPLS features from parent device
- net: bonding: Inherit MPLS features from slave devices
- net/mlx5e: Move to HW checksumming advertising
* LIO hanging in iscsit_free_session and iscsit_stop_session (LP: #1871688)
- scsi: target: remove boilerplate code
- scsi: target: fix hang when multiple threads try to destroy the same iscsi
session
- scsi: target: iscsi: calling iscsit_stop_session() inside
iscsit_close_session() has no effect
* Add hw timestamps to received skbs in peak_canfd (LP: #1874124)
- can: peak_canfd: provide hw timestamps in rx skbs
* Bionic update: upstream stable patchset 2020-04-23 (LP: #1874502)
- ARM: dts: sun8i-a83t-tbs-a711: HM5065 doesn't like such a high voltage
- bus: sunxi-rsb: Return correct data when mixing 16-bit and 8-bit reads
- net: vxge: fix wrong __VA_ARGS__ usage
- hinic: fix a bug of waitting for IO stopped
- hinic: fix wrong para of wait_for_completion_timeout
- cxgb4/ptp: pass the sign of offset delta in FW CMD
- qlcnic: Fix bad kzalloc null test
- i2c: st: fix missing struct parameter description
- firmware: arm_sdei: fix double-lock on hibernate with shared events
- null_blk: Fix the null_add_dev() error path
- null_blk: Handle null_add_dev() failures properly
- null_blk: fix spurious IO errors after failed past-wp access
- xhci: bail out early if driver can't accress host in resume
- x86: Don't let pgprot_modify() change the page encryption bit
- block: keep bdi->io_pages in sync with max_sectors_kb for stacked devices
- irqchip/versatile-fpga: Handle chained IRQs properly
- sched: Avoid scale real weight down to zero
- selftests/x86/ptrace_syscall_32: Fix no-vDSO segfault
- PCI/switchtec: Fix init_completion race condition with poll_wait()
- libata: Remove extra scsi_host_put() in ata_scsi_add_hosts()
- gfs2: Don't demote a glock until its revokes are written
- x86/boot: Use unsigned comparison for addresses
- efi/x86: Ignore the memory attributes table on i386
- genirq/irqdomain: Check pointer in irq_domain_alloc_irqs_hierarchy()
- block: Fix use-after-free issue accessing struct io_cq
- usb: dwc3: core: add support for disabling SS instances in park mode
- irqchip/gic-v4: Provide irq_retrigger to avoid circular locking dependency
- md: check arrays is suspended in mddev_detach before call quiesce
operations
- locking/lockdep: Avoid recursion in lockdep_count_{for,back}ward_deps()
- block, bfq: fix use-after-free in bfq_idle_slice_timer_body
- btrfs: qgroup: ensure qgroup_rescan_running is only set when the worker is
at least queued
- btrfs: remove a BUG_ON() from merge_reloc_roots()
- btrfs: track reloc roots based on their commit root bytenr
- uapi: rename ext2_swab() to swab() and share globally in swab.h
- slub: improve bit diffusion for freelist ptr obfuscation
- ASoC: fix regwmask
- ASoC: dapm: connect virtual mux with default value
- ASoC: dpcm: allow start or stop during pause for backend
- ASoC: topology: use name_prefix for new kcontrol
- usb: gadget: f_fs: Fix use after free issue as part of queue failure
- usb: gadget: composite: Inform controller driver of self-powered
- ALSA: usb-audio: Add mixer workaround for TRX40 and co
- ALSA: hda: Add driver blacklist
- ALSA: hda: Fix potential access overflow in beep helper
- ALSA: ice1724: Fix invalid access for enumerated ctl items
- ALSA: pcm: oss: Fix regression by buffer overflow fix
- ALSA:
[Touch-packages] [Bug 1878553] Re: Ubuntu could not install Virtualbox Guest addons
Thank you for the bug report, indeed there is something weird with software-properties Starting a focal iso in virtual, sofware-properties-gtk lists VMware drivers with only with continue manual mode available, but 'sudo ubuntu- drivers install' does install open-vm-tools seems rather an issue with the gui ** Tags added: focal rls-ff-incoming ** Package changed: ubuntu-drivers-common (Ubuntu) => software- properties (Ubuntu) -- 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/1878553 Title: Ubuntu could not install Virtualbox Guest addons Status in software-properties package in Ubuntu: New Bug description: It seems that Ubuntu is not able to install the VirtualBox Guest add- ons even Ubuntu is able to detect it. See Attachement. Ubuntu 20.04 Basic install after Reboot, Update and Reboot again. Similar Tickets in Launchpad but really old: https://bugs.launchpad.net/ubuntu/+source/ubuntu-drivers-common/+bug/1434579 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1878553/+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 1878553] [NEW] Ubuntu could not install Virtualbox Guest addons
You have been subscribed to a public bug: It seems that Ubuntu is not able to install the VirtualBox Guest add-ons even Ubuntu is able to detect it. See Attachement. Ubuntu 20.04 Basic install after Reboot, Update and Reboot again. Similar Tickets in Launchpad but really old: https://bugs.launchpad.net/ubuntu/+source/ubuntu-drivers-common/+bug/1434579 ** Affects: software-properties (Ubuntu) Importance: Undecided Status: New ** Tags: focal guestaddon innotek rls-ff-incoming virtualbox virtualisation -- Ubuntu could not install Virtualbox Guest addons https://bugs.launchpad.net/bugs/1878553 You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to software-properties 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 1879206] Re: cups hplip not install printer
In the properties window of the printer connected as USB it indicates the absence of an HP file, on test printing with network installation the printer does not report an error, but does not connect. Inattiva - Il file "/usr/lib/cups/backend/hp" non è disponibile: No such file or directory ** Attachment added: "Localhost.png" https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1879206/+attachment/5373331/+files/Localhost.png -- 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/1879206 Title: cups hplip not install printer Status in cups package in Ubuntu: New Bug description: After upgrading to Ubuntu 20.04 I can't print anymore. Description: Ubuntu 20.04 LTS Release: 20.04 cups: Installato: 2.3.1-9ubuntu1.1 Candidato: 2.3.1-9ubuntu1.1 Tabella versione: *** 2.3.1-9ubuntu1.1 500 500 http://it.archive.ubuntu.com/ubuntu focal-updates/main amd64 Packages 500 http://security.ubuntu.com/ubuntu focal-security/main amd64 Packages 100 /var/lib/dpkg/status 2.3.1-9ubuntu1 500 500 http://it.archive.ubuntu.com/ubuntu focal/main amd64 Packages hplip: Installato: 3.20.3+dfsg0-2 Candidato: 3.20.3+dfsg0-2 Tabella versione: *** 3.20.3+dfsg0-2 500 500 http://it.archive.ubuntu.com/ubuntu focal/main amd64 Packages 100 /var/lib/dpkg/status I tried to reinstall the printer, but it is not being re-saved by cups / hplip ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: cups 2.3.1-9ubuntu1.1 ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30 Uname: Linux 5.4.0-29-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Mon May 18 02:24:07 2020 InstallationDate: Installed on 2020-05-17 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) Lpstat: device for DeskJet_3630: hp:/usb/DeskJet_3630_series?serial=CN8AM7H3230658 MachineType: LENOVO 80G0 Papersize: a4 PpdFiles: Error: command ['fgrep', '-H', '*NickName', '/etc/cups/ppd/DeskJet_3630.ppd'] failed with exit code 2: grep: /etc/cups/ppd/DeskJet_3630.ppd: Permission denied ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-29-generic root=UUID=6a8469e0-ecea-4a86-8040-b0caaa938fe4 ro quiet splash vt.handoff=7 SourcePackage: cups UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/18/2014 dmi.bios.vendor: LENOVO dmi.bios.version: A7CN40WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: Lancer 5A6 dmi.board.vendor: LENOVO dmi.board.version: SDK0F82993WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo G50-30 dmi.modalias: dmi:bvnLENOVO:bvrA7CN40WW:bd07/18/2014:svnLENOVO:pn80G0:pvrLenovoG50-30:rvnLENOVO:rnLancer5A6:rvrSDK0F82993WIN:cvnLENOVO:ct10:cvrLenovoG50-30: dmi.product.family: IDEAPAD dmi.product.name: 80G0 dmi.product.sku: LENOVO_MT_80G0_BU_idea_FM_Lenovo G50-30 dmi.product.version: Lenovo G50-30 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1879206/+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 1878617] Re: Apple pages file type should be added to MIME types
As requested, here is an example of an Apple Pages document, taken from an online templates website. ** Attachment added: "New Job Resignation Letter.pages" https://bugs.launchpad.net/ubuntu/+source/mime-support/+bug/1878617/+attachment/5373328/+files/New%20Job%20Resignation%20Letter.pages ** Changed in: mime-support (Ubuntu) Status: Incomplete => New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mime-support in Ubuntu. https://bugs.launchpad.net/bugs/1878617 Title: Apple pages file type should be added to MIME types Status in mime-support package in Ubuntu: New Bug description: LibreOffice can open .pages files (from Apple pages). However, the mime type for these files is incorrectly just application/zip: $ file --mime-type example.pages example.pages: application/zip Instead, it should be application/vnd.apple.pages . This would allow the user to associate LibreOffice Writer with these types of files, and use it to open this file. (LibreOffice Writer can open .pages files) Apple Keynote files should have this MIME type: application/vnd.apple.keynote Apple Numbers files should have this MIME type: application/vnd.apple.numbers ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: mime-support 3.64ubuntu1 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: ubuntu:GNOME Date: Thu May 14 14:46:40 2020 InstallationDate: Installed on 2018-11-11 (550 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) PackageArchitecture: all SourcePackage: mime-support UpgradeStatus: Upgraded to focal on 2020-04-18 (25 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mime-support/+bug/1878617/+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 1878617] Re: Apple pages file type should be added to MIME types
I created a bug report in shared-mime-info's issues tracker here: https://gitlab.freedesktop.org/xdg/shared-mime-info/-/issues/136 ** Bug watch added: gitlab.freedesktop.org/xdg/shared-mime-info/-/issues #136 https://gitlab.freedesktop.org/xdg/shared-mime-info/-/issues/136 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mime-support in Ubuntu. https://bugs.launchpad.net/bugs/1878617 Title: Apple pages file type should be added to MIME types Status in mime-support package in Ubuntu: New Bug description: LibreOffice can open .pages files (from Apple pages). However, the mime type for these files is incorrectly just application/zip: $ file --mime-type example.pages example.pages: application/zip Instead, it should be application/vnd.apple.pages . This would allow the user to associate LibreOffice Writer with these types of files, and use it to open this file. (LibreOffice Writer can open .pages files) Apple Keynote files should have this MIME type: application/vnd.apple.keynote Apple Numbers files should have this MIME type: application/vnd.apple.numbers ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: mime-support 3.64ubuntu1 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: ubuntu:GNOME Date: Thu May 14 14:46:40 2020 InstallationDate: Installed on 2018-11-11 (550 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) PackageArchitecture: all SourcePackage: mime-support UpgradeStatus: Upgraded to focal on 2020-04-18 (25 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mime-support/+bug/1878617/+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 1509717] Re: Wily LVM-RAID1 – md: personality for level 1 is not loaded
verified in bionic Did all the steps (install vm, create pv, extend pv, remove dmadm, upgrade). It booted after the upgrade to 2.02.176-4.1ubuntu3.18.04.3, and it failed again following a downgrade to the 2.02.176-4.1ubuntu3.18.04.2 from updates pocket. ** Tags removed: verification-needed-bionic ** Tags added: verification-done-bionic ** Tags removed: id-5d0ba914f340e31a8e9f2cf1 removal-candidate ** Tags added: id-5d0ba914f340e31a8e9f2cf -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lvm2 in Ubuntu. https://bugs.launchpad.net/bugs/1509717 Title: Wily LVM-RAID1 – md: personality for level 1 is not loaded Status in linux package in Ubuntu: Invalid Status in lvm2 package in Ubuntu: Fix Released Status in linux source package in Bionic: Invalid Status in lvm2 source package in Bionic: Fix Committed Status in linux source package in Cosmic: Invalid Status in lvm2 source package in Cosmic: Won't Fix Status in linux source package in Disco: Invalid Status in lvm2 source package in Disco: Won't Fix Status in linux source package in Eoan: Invalid Status in lvm2 source package in Eoan: Fix Committed Status in lvm2 package in Debian: Incomplete Bug description: [Impact] system does not boot after converting lvm volume to raid1 w/o having mdadm installed. [Test case] 1. Install server with subiquity to LVM 2. Add second disk to it 3. Run pvcreate /dev/vdb 4. Run vgextend ubuntu-vg /dev/vdb 5. Run lvconvert -m1 --type raid1 ubuntu-vg/lv Reboot and check that it still boots. 6. Remove mdadm 7. Upgrade to lvm2 from proposed Reboot and check that it still boots. 8. Downgrade lvm2 to release Reboot and check that it fails to boot [Regression potential] Not really anything, we just add the raid1 module to initramfs, so it might be loaded during boot, and raid1 logical volumes might appear earlier. [Original bug report] After upgrading to Wily, raid1 LVs don't activate during the initrd phase. Since the root LV is also RAID1-mirrored, the system doesn't boot. I get the following message each time LVM tries to activate a raid1 LV: md: personality for level 1 is not loaded! Everything was fine with Vivid. I had to downgrade to Vivid kernel (3.19.0-30) to get my system to a usable state. I pretty much hope it to be a temporary workaround and I'll get the new 4.2.0 kernel work with Wily in days. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1509717/+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 1870359] Re: My machine as Wi-Fi Hotspot broken after upgrade to 20.04
Could you try if it works better in nm-connection-editor? Could you add your 'journalctl -b 0' log after triggering the issue? It would also be useful to have details on how it's not working. Is the menu option disabled? do you fail to connect? do you connect by have no data working? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1870359 Title: My machine as Wi-Fi Hotspot broken after upgrade to 20.04 Status in network-manager package in Ubuntu: Confirmed Bug description: I have a machine with a wired network connection and a wifi card. I've been using the machine as a wireless router and server in my house. I've attached a screenshot of the Wi-Fi network settings. It looks as expected. Upon updating to 20.04, none of my machines can use the connection. The linux machine will not connect. The windows machine will connect but will not have internet. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: network-manager 1.22.10-1ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.11-0ubuntu22 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Apr 2 15:47:02 2020 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2015-09-30 (1645 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) IpRoute: default via 192.168.0.1 dev eth0 proto static metric 100 169.254.0.0/16 dev eth0 scope link metric 1000 192.168.0.0/24 dev eth0 proto kernel scope link src 192.168.0.100 metric 100 SourcePackage: network-manager UpgradeStatus: Upgraded to focal on 2020-04-02 (0 days ago) WifiSyslog: mtime.conffile..etc.NetworkManager.NetworkManager.conf: 2018-01-13T14:45:42.987041 nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.22.10 connected started full enabled enabled enabled enabled enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1870359/+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
