[Desktop-packages] [Bug 1771749] [NEW] Ethernet connection lost after few minutes since starting
Public bug reported: This is the same bug I notified at Bug #1770848 but with a more precise selection of (what I think it is) the package affected and a better description. I made a few days ago a fresh install of the Kubuntu 18.04 LTS and it is most everything Ok, but -I think that- the network-manager has a problem. In the last LTS version, Kubuntu 16.04, nor in any Linux version if I remember well, I never lost connection through Ethernet (the only Internet connection with our desktop PC), but the Bionic Beaver loses the connection every now and then, perhaps within few minutes or hours, but several times per day. When the connection is lost, I note that it disappears any info even mention to any network into the network window and the network manager icon becomes red color. Not matter if I unplug and then plug the ethernet cable again, the ethernet connection is not longer detected and only restarting the PC makes the connection to work again. Incidentally, I also have noticed with this version of Kubuntu 18.04 that in my laptop there is also now a similar problem with the scanner: If I plug it in some USB port of the laptop once Kubuntu 18.04 is already running, it's not detected by Xsane. I have to plug it in before than pressing the power button or at the time of starting the OS, for the scanner to be detected by the scanning program (and then only works with Xsane, not if I use Simple Scan or Skanlite, even when it works under Xsane), as I said in the Bug #1771525 and, evenly, if I unplug the scanner cable from the USB port it is not detected anymore when plugging it again, and only restarting the laptop makes it to be detected. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: network-manager 1.10.6-2ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 CurrentDesktop: KDE Date: Thu May 17 08:24:23 2018 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2018-05-11 (5 days ago) InstallationMedia: Kubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) IpRoute: default via 192.168.1.1 dev enp0s7 proto static metric 100 169.254.0.0/16 dev enp0s7 scope link metric 1000 192.168.1.0/24 dev enp0s7 proto kernel scope link src 192.168.1.3 metric 100 IwConfig: enp0s7no wireless extensions. lono wireless extensions. NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true PciNetwork: RfKill: SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) nmcli-con: NAME UUID TYPE TIMESTAMP TIMESTAMP-REAL AUTOCONNECT AUTOCONNECT-PRIORITY READONLY DBUS-PATH ACTIVE DEVICE STATE ACTIVE-PATH SLAVE Conexión cableada 1 1cc37db8-0db8-3887-acf2-59fbbcd0cb1c ethernet 1526538083 jue 17 may 2018 08:21:23 CEST yes 4294967196 no/org/freedesktop/NetworkManager/Settings/1 yes enp0s7 activated /org/freedesktop/NetworkManager/ActiveConnection/1 -- nmcli-dev: DEVICE TYPE STATE DBUS-PATH CONNECTION CON-UUID CON-PATH enp0s7 ethernet connected /org/freedesktop/NetworkManager/Devices/2 Conexión cableada 1 1cc37db8-0db8-3887-acf2-59fbbcd0cb1c /org/freedesktop/NetworkManager/ActiveConnection/1 lo loopback unmanaged /org/freedesktop/NetworkManager/Devices/1 -- ---- nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.10.6 connected started full enabled enabled enabled enabled enabled ** Affects: network-manager (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1771749 Title: Ethernet connection lost after few minutes since starting Status in network-manager package in Ubuntu: New Bug description: This is the same bug I notified at Bug #1770848 but with a more precise selection of (what I think it is) the package affected and a better description. I made a few days ago a fresh install of the Kubuntu 18.04 LTS and it is most everything Ok, but -I think that- the network-manager has a problem. In the last LTS version, Kubuntu 16.04, nor in any Linux version if I remember well, I never lost connection through Ethernet (the only Internet connection with our desktop PC), but the Bionic Beaver loses the connection every now an
[Desktop-packages] [Bug 1751252] Update Released
The verification of the Stable Release Update for ubiquity has completed
successfully and the package has now been 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 Desktop
Packages, which is subscribed to cairo in Ubuntu.
https://bugs.launchpad.net/bugs/1751252
Title:
[regression] ubiquity crashed in debconf.py:104 with ValueError:
invalid literal for int() with base 10: ''
Status in cairo:
Confirmed
Status in OEM Priority Project:
Triaged
Status in cairo package in Ubuntu:
In Progress
Status in ubiquity package in Ubuntu:
Fix Released
Status in cairo source package in Bionic:
In Progress
Status in ubiquity source package in Bionic:
Fix Released
Bug description:
* Impact
The Ubuntu installer crashes on some machines (seems more often on hiDPI
machines (QHD/UHD etc)).
* Test case
Try installing Ubuntu on an hidpi machine, it should complete installation
instead of crashing.
* Regression potential
The fix in ubiquity touches the code handle uid drop/privilege, that can have
unexpected side effects so we need proper/complete testing of the installer
--
Update: Actually the crash occurs on slow-ish systems due to a race
condition. It's not strictly only hi-DPI machines - that's just the
most common place it is experienced.
---
https://errors.ubuntu.com/problem/82f7f7e7923663c7b2123c7f1f49af29f6ff4d77
https://errors.ubuntu.com/problem/735a2b847e0eeab6c8a7b954de5110e43889be15
https://errors.ubuntu.com/problem/dcd4c9da5ee0cc6d36324446e0e49d39705c90b7
https://errors.ubuntu.com/problem/cb82f70f9ede07369e8104da9ddf87e28b42257d
https://errors.ubuntu.com/problem/84a5563af3d2b85f098da832ece4cb8450bfd524
---
WORKAROUND:
1. Boot into the live session.
2. Settings > Devices > Displays > Scale = 100%
3. Click Apply.
4. Proceed with installation: Click "Install Ubuntu 18.04 LTS".
---
Crashed in a VM in the middle of installation. The host is Bionic up
to date.
From the journal
Feb 23 12:52:27 ubuntu kernel: traps: ubiquity[2646] trap int3
ip:7f5a76936961 sp:7ffde5090c50 error:0 in
libglib-2.0.so.0.5400.1[7f5a768e6000+111000]
Feb 23 12:52:41 ubuntu /install.py[6858]: Exception during installation:
Feb 23 12:52:41 ubuntu /install.py[6858]: Traceback (most recent call last):
Feb 23 12:52:41 ubuntu /install.py[6858]: File
"/usr/share/ubiquity/install.py", line 757, in
Feb 23 12:52:41 ubuntu /install.py[6858]: install.run()
Feb 23 12:52:41 ubuntu /install.py[6858]: File
"/usr/share/ubiquity/install.py", line 135, in run
Feb 23 12:52:41 ubuntu /install.py[6858]: self.copy_all()
Feb 23 12:52:41 ubuntu /install.py[6858]: File
"/usr/share/ubiquity/install.py", line 505, in copy_all
Feb 23 12:52:41 ubuntu /install.py[6858]: self.db.progress('SET', 10 +
copy_progress)
Feb 23 12:52:41 ubuntu /install.py[6858]: File
"/usr/lib/python3/dist-packages/debconf.py", line 83, in
Feb 23 12:52:41 ubuntu /install.py[6858]: lambda *args, **kw:
self.command(command, *args, **kw))
Feb 23 12:52:41 ubuntu /install.py[6858]: File
"/usr/lib/python3/dist-packages/debconf.py", line 104, in command
Feb 23 12:52:41 ubuntu /install.py[6858]: status = int(status)
Feb 23 12:52:41 ubuntu /install.py[6858]: ValueError: invalid literal for
int() with base 10: ''
ProblemType: Crash
DistroRelease: Ubuntu 18.04
Package: ubiquity 18.04.1
ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13
Uname: Linux 4.13.0-32-generic x86_64
ApportVersion: 2.20.8-0ubuntu10
Architecture: amd64
CasperVersion: 1.388
Date: Fri Feb 23 12:52:28 2018
ExecutablePath: /usr/lib/ubiquity/bin/ubiquity
InstallCmdLine: file=/cdrom/preseed/ubuntu.seed boot=casper
initrd=/casper/initrd.lz quiet splash --- keyboard-configuration/layoutcode=fr
keyboard-configuration/variantcode=oss
InterpreterPath: /usr/bin/python3.6
LiveMediaBuild: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180222)
ProcCmdline: /usr/bin/python3 /usr/lib/ubiquity/bin/ubiquity -d
ProcEnviron:
TERM=xterm-256color
PATH=(custom, no user)
LANG=C.UTF-8
SHELL=/bin/bash
Python3Details: /usr/bin/python3.6, Python 3.6.4+, python3-minimal, 3.6.4-1
PythonDetails: /usr/bin/python2.7, Python 2.7.14+, python-minimal, 2.7.14-4
Signal: 5
SourcePackage: ubiquity
StacktraceTop:
?? () from /usr/lib/x86_64-linux-gnu/libX11.so.6
?? () from /usr/lib/x86_64-linux-gnu/libX11.so.6
_XEventsQueued () from /usr/lib/x86_64-linux-gnu/libX11.so.6
XPending () from /usr/lib/x86_64-linux-gnu/libX11.so.6
?? () from /usr/lib/x86_64-linux-gnu/libgdk-3.so.0
Title: ub
[Desktop-packages] [Bug 1751252] Re: [regression] ubiquity crashed in debconf.py:104 with ValueError: invalid literal for int() with base 10: ''
This bug was fixed in the package ubiquity - 18.04.14.1
---
ubiquity (18.04.14.1) bionic; urgency=medium
[ Iain Lane ]
* Update Vcs-* for git migration
[ Andrea Azzarone ]
* misc.py: Restore the corrent euid in regain_privileges_save. Calling
regain_privileges_save should restore the effective user-id to the one
before the call to drop_privileges_save. We need to call os.setresuid and
os.setresgid twice to avoid permission issues when calling os.setgroups.
(LP: #1751252)
-- Iain Lane Tue, 08 May 2018 15:22:49 +0100
** Changed in: ubiquity (Ubuntu Bionic)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to cairo in Ubuntu.
https://bugs.launchpad.net/bugs/1751252
Title:
[regression] ubiquity crashed in debconf.py:104 with ValueError:
invalid literal for int() with base 10: ''
Status in cairo:
Confirmed
Status in OEM Priority Project:
Triaged
Status in cairo package in Ubuntu:
In Progress
Status in ubiquity package in Ubuntu:
Fix Released
Status in cairo source package in Bionic:
In Progress
Status in ubiquity source package in Bionic:
Fix Released
Bug description:
* Impact
The Ubuntu installer crashes on some machines (seems more often on hiDPI
machines (QHD/UHD etc)).
* Test case
Try installing Ubuntu on an hidpi machine, it should complete installation
instead of crashing.
* Regression potential
The fix in ubiquity touches the code handle uid drop/privilege, that can have
unexpected side effects so we need proper/complete testing of the installer
--
Update: Actually the crash occurs on slow-ish systems due to a race
condition. It's not strictly only hi-DPI machines - that's just the
most common place it is experienced.
---
https://errors.ubuntu.com/problem/82f7f7e7923663c7b2123c7f1f49af29f6ff4d77
https://errors.ubuntu.com/problem/735a2b847e0eeab6c8a7b954de5110e43889be15
https://errors.ubuntu.com/problem/dcd4c9da5ee0cc6d36324446e0e49d39705c90b7
https://errors.ubuntu.com/problem/cb82f70f9ede07369e8104da9ddf87e28b42257d
https://errors.ubuntu.com/problem/84a5563af3d2b85f098da832ece4cb8450bfd524
---
WORKAROUND:
1. Boot into the live session.
2. Settings > Devices > Displays > Scale = 100%
3. Click Apply.
4. Proceed with installation: Click "Install Ubuntu 18.04 LTS".
---
Crashed in a VM in the middle of installation. The host is Bionic up
to date.
From the journal
Feb 23 12:52:27 ubuntu kernel: traps: ubiquity[2646] trap int3
ip:7f5a76936961 sp:7ffde5090c50 error:0 in
libglib-2.0.so.0.5400.1[7f5a768e6000+111000]
Feb 23 12:52:41 ubuntu /install.py[6858]: Exception during installation:
Feb 23 12:52:41 ubuntu /install.py[6858]: Traceback (most recent call last):
Feb 23 12:52:41 ubuntu /install.py[6858]: File
"/usr/share/ubiquity/install.py", line 757, in
Feb 23 12:52:41 ubuntu /install.py[6858]: install.run()
Feb 23 12:52:41 ubuntu /install.py[6858]: File
"/usr/share/ubiquity/install.py", line 135, in run
Feb 23 12:52:41 ubuntu /install.py[6858]: self.copy_all()
Feb 23 12:52:41 ubuntu /install.py[6858]: File
"/usr/share/ubiquity/install.py", line 505, in copy_all
Feb 23 12:52:41 ubuntu /install.py[6858]: self.db.progress('SET', 10 +
copy_progress)
Feb 23 12:52:41 ubuntu /install.py[6858]: File
"/usr/lib/python3/dist-packages/debconf.py", line 83, in
Feb 23 12:52:41 ubuntu /install.py[6858]: lambda *args, **kw:
self.command(command, *args, **kw))
Feb 23 12:52:41 ubuntu /install.py[6858]: File
"/usr/lib/python3/dist-packages/debconf.py", line 104, in command
Feb 23 12:52:41 ubuntu /install.py[6858]: status = int(status)
Feb 23 12:52:41 ubuntu /install.py[6858]: ValueError: invalid literal for
int() with base 10: ''
ProblemType: Crash
DistroRelease: Ubuntu 18.04
Package: ubiquity 18.04.1
ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13
Uname: Linux 4.13.0-32-generic x86_64
ApportVersion: 2.20.8-0ubuntu10
Architecture: amd64
CasperVersion: 1.388
Date: Fri Feb 23 12:52:28 2018
ExecutablePath: /usr/lib/ubiquity/bin/ubiquity
InstallCmdLine: file=/cdrom/preseed/ubuntu.seed boot=casper
initrd=/casper/initrd.lz quiet splash --- keyboard-configuration/layoutcode=fr
keyboard-configuration/variantcode=oss
InterpreterPath: /usr/bin/python3.6
LiveMediaBuild: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180222)
ProcCmdline: /usr/bin/python3 /usr/lib/ubiquity/bin/ubiquity -d
ProcEnviron:
TERM=xterm-256color
PATH=(custom, no user)
LANG=C.UTF-8
SHELL=/bin/bash
Python3Details: /usr/bin/python3.6, Python 3.6.4+, python3-minimal, 3.6.4-1
PythonDetails: /usr/bin/python2.7, Python 2.7.14+, python-minimal, 2.7.14-4
Signal: 5
SourcePackage: ubiquity
StacktraceTop:
?? () from /usr/lib/x86_64-linux-gnu/libX11.so.6
?? () from /usr/lib/x86_64-linux-gnu/libX11.so.6
[Desktop-packages] [Bug 1771757] [NEW] Ubuntu doesn't detect device on USB 3.1 Gen 2 port
Public bug reported: Ubuntu does't detect the device when I plug a USB Flash drive onto the USB 3.1 Gen 2 port on my motherboard. I can't find the device in lsusb output. If I reboot the system with the drive plugged, I can mount the drive in file manager. If I unplug and plug it again, Ubuntu doesn't detect the device. My motherboard is ASUS ROG STRIX B360-G. Tried stock bionic and latest v4.16/v4.17 mainline kernels. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7 Uname: Linux 4.16.9-041609-generic x86_64 ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: KDE Date: Thu May 17 15:19:47 2018 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: kubuntu DkmsStatus: virtualbox, 5.2.10, 4.15.0-20-generic, x86_64: installed virtualbox, 5.2.10, 4.16.9-041609-generic, x86_64: installed ExtraDebuggingInterest: I just need to know a workaround GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Baffin [Polaris11] [1002:67ff] (rev cf) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Baffin [Radeon RX 560] [1043:04be] InstallationDate: Installed on 2018-03-03 (74 days ago) InstallationMedia: Kubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180303) MachineType: System manufacturer System Product Name ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.16.9-041609-generic root=UUID=3fd33ecf-eee9-442d-b5e6-8c9e4344b643 ro resume=UUID=3fd33ecf-eee9-442d-b5e6-8c9e4344b643 resume_offset=34816 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/23/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0602 dmi.board.asset.tag: Default string dmi.board.name: ROG STRIX B360-G GAMING dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0602:bd03/23/2018:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnROGSTRIXB360-GGAMING:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.91-2 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.0~rc5-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.0~rc5-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 ** Affects: ubuntu Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic kubuntu ** Package changed: xorg (Ubuntu) => ubuntu -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1771757 Title: Ubuntu doesn't detect device on USB 3.1 Gen 2 port Status in Ubuntu: New Bug description: Ubuntu does't detect the device when I plug a USB Flash drive onto the USB 3.1 Gen 2 port on my motherboard. I can't find the device in lsusb output. If I reboot the system with the drive plugged, I can mount the drive in file manager. If I unplug and plug it again, Ubuntu doesn't detect the device. My motherboard is ASUS ROG STRIX B360-G. Tried stock bionic and latest v4.16/v4.17 mainline kernels. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7 Uname: Linux 4.16.9-041609-generic x86_64 ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: KDE Date: Thu May 17 15:19:47 2018 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: kubuntu DkmsStatus: virtualbox, 5.2.10, 4.15.0-20-generic, x86_64: installed virtualbox, 5.2.10, 4.16.9-041609-generic, x86_64: installed ExtraDebuggingInterest: I just need to know a workaround GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Baffin [Polaris11] [1002:67ff] (rev cf) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Baffin [Radeon RX 560] [1043:04be] InstallationDate: Installed on 2018-03-03 (74 days ago) InstallationMedia: Kubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180303) MachineType: System manufacturer System Product Name ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.16.9-041609-generic root=UUID=3fd33ecf-eee9-442d-b5e6-8c9e4344b643 ro resume=UUID=3fd33ecf-eee9-442d-b5e6-8c9e4344b643 resume_offset=34816 SourcePackage: xorg Sympto
[Desktop-packages] [Bug 1771749] Re: Ethernet connection lost after few minutes since starting
** Also affects: linux (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1771749 Title: Ethernet connection lost after few minutes since starting Status in linux package in Ubuntu: Incomplete Status in network-manager package in Ubuntu: New Bug description: This is the same bug I notified at Bug #1770848 but with a more precise selection of (what I think it is) the package affected and a better description. I made a few days ago a fresh install of the Kubuntu 18.04 LTS and it is most everything Ok, but -I think that- the network-manager has a problem. In the last LTS version, Kubuntu 16.04, nor in any Linux version if I remember well, I never lost connection through Ethernet (the only Internet connection with our desktop PC), but the Bionic Beaver loses the connection every now and then, perhaps within few minutes or hours, but several times per day. When the connection is lost, I note that it disappears any info even mention to any network into the network window and the network manager icon becomes red color. Not matter if I unplug and then plug the ethernet cable again, the ethernet connection is not longer detected and only restarting the PC makes the connection to work again. Incidentally, I also have noticed with this version of Kubuntu 18.04 that in my laptop there is also now a similar problem with the scanner: If I plug it in some USB port of the laptop once Kubuntu 18.04 is already running, it's not detected by Xsane. I have to plug it in before than pressing the power button or at the time of starting the OS, for the scanner to be detected by the scanning program (and then only works with Xsane, not if I use Simple Scan or Skanlite, even when it works under Xsane), as I said in the Bug #1771525 and, evenly, if I unplug the scanner cable from the USB port it is not detected anymore when plugging it again, and only restarting the laptop makes it to be detected. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: network-manager 1.10.6-2ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 CurrentDesktop: KDE Date: Thu May 17 08:24:23 2018 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2018-05-11 (5 days ago) InstallationMedia: Kubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) IpRoute: default via 192.168.1.1 dev enp0s7 proto static metric 100 169.254.0.0/16 dev enp0s7 scope link metric 1000 192.168.1.0/24 dev enp0s7 proto kernel scope link src 192.168.1.3 metric 100 IwConfig: enp0s7no wireless extensions. lono wireless extensions. NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true PciNetwork: RfKill: SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) nmcli-con: NAME UUID TYPE TIMESTAMP TIMESTAMP-REAL AUTOCONNECT AUTOCONNECT-PRIORITY READONLY DBUS-PATH ACTIVE DEVICE STATE ACTIVE-PATH SLAVE Conexión cableada 1 1cc37db8-0db8-3887-acf2-59fbbcd0cb1c ethernet 1526538083 jue 17 may 2018 08:21:23 CEST yes 4294967196 no/org/freedesktop/NetworkManager/Settings/1 yes enp0s7 activated /org/freedesktop/NetworkManager/ActiveConnection/1 -- nmcli-dev: DEVICE TYPE STATE DBUS-PATH CONNECTION CON-UUID CON-PATH enp0s7 ethernet connected /org/freedesktop/NetworkManager/Devices/2 Conexión cableada 1 1cc37db8-0db8-3887-acf2-59fbbcd0cb1c /org/freedesktop/NetworkManager/ActiveConnection/1 lo loopback unmanaged /org/freedesktop/NetworkManager/Devices/1 -- ---- nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.10.6 connected started full enabled enabled enabled enabled enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1771749/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1771749] 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 1771749 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 Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1771749 Title: Ethernet connection lost after few minutes since starting Status in linux package in Ubuntu: Incomplete Status in network-manager package in Ubuntu: New Bug description: This is the same bug I notified at Bug #1770848 but with a more precise selection of (what I think it is) the package affected and a better description. I made a few days ago a fresh install of the Kubuntu 18.04 LTS and it is most everything Ok, but -I think that- the network-manager has a problem. In the last LTS version, Kubuntu 16.04, nor in any Linux version if I remember well, I never lost connection through Ethernet (the only Internet connection with our desktop PC), but the Bionic Beaver loses the connection every now and then, perhaps within few minutes or hours, but several times per day. When the connection is lost, I note that it disappears any info even mention to any network into the network window and the network manager icon becomes red color. Not matter if I unplug and then plug the ethernet cable again, the ethernet connection is not longer detected and only restarting the PC makes the connection to work again. Incidentally, I also have noticed with this version of Kubuntu 18.04 that in my laptop there is also now a similar problem with the scanner: If I plug it in some USB port of the laptop once Kubuntu 18.04 is already running, it's not detected by Xsane. I have to plug it in before than pressing the power button or at the time of starting the OS, for the scanner to be detected by the scanning program (and then only works with Xsane, not if I use Simple Scan or Skanlite, even when it works under Xsane), as I said in the Bug #1771525 and, evenly, if I unplug the scanner cable from the USB port it is not detected anymore when plugging it again, and only restarting the laptop makes it to be detected. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: network-manager 1.10.6-2ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 CurrentDesktop: KDE Date: Thu May 17 08:24:23 2018 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2018-05-11 (5 days ago) InstallationMedia: Kubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) IpRoute: default via 192.168.1.1 dev enp0s7 proto static metric 100 169.254.0.0/16 dev enp0s7 scope link metric 1000 192.168.1.0/24 dev enp0s7 proto kernel scope link src 192.168.1.3 metric 100 IwConfig: enp0s7no wireless extensions. lono wireless extensions. NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true PciNetwork: RfKill: SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) nmcli-con: NAME UUID TYPE TIMESTAMP TIMESTAMP-REAL AUTOCONNECT AUTOCONNECT-PRIORITY READONLY DBUS-PATH ACTIVE DEVICE STATE ACTIVE-PATH SLAVE Conexión cableada 1 1cc37db8-0db8-3887-acf2-59fbbcd0cb1c ethernet 1526538083 jue 17 may 2018 08:21:23 CEST yes 4294967196 no/org/freedesktop/NetworkManager/Settings/1 yes enp0s7 activated /org/freedesktop/NetworkManager/ActiveConnection/1 -- nmcli-dev: DEVICE TYPE STATE DBUS-PATH CONNECTION CON-UUID CON-PATH enp0s7 ethernet connected /org/freedesktop/NetworkManager/Devices/2 Conexión cableada 1 1cc37db8-0db8-3887-acf2-59fbbcd0cb1c /org/freedesktop/NetworkManager/ActiveConnection/1 lo loopback unmanaged /org/freedesktop/NetworkManager/Devices/1 -- ---- nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN ru
[Desktop-packages] [Bug 1759468] Re: gnome-control-center (11) gtk_style_context_clear_property_cache → gtk_css_widget_node_update_style → gtk_css_node_ensure_style → gtk_css_node_ensure_style → gtk_c
@andyrock, is https://gitlab.gnome.org/GNOME/gnome-control- center/merge_requests/49/diffs the correct fix for that segfault? it seems only half of the change from master, is that enough? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1759468 Title: gnome-control-center (11) gtk_style_context_clear_property_cache → gtk_css_widget_node_update_style → gtk_css_node_ensure_style → gtk_css_node_ensure_style → gtk_css_node_validate_internal Status in gnome-control-center package in Ubuntu: In Progress Status in gtk+3.0 package in Ubuntu: Fix Released Bug description: * Impact gnome-control-center sometimes hits a segfault * Test case - Check if the e.u.c reports stop with the new version or - Open GNOME Control Center - Go to Devices->Display panel - Close the window - Open GNOME Control Center again (in overview mode) the settings should open without error * Regression potential check the panels can be opened without error and that switching between them works as well -- The Ubuntu Error Tracker has been receiving reports about a problem regarding gnome-control-center. This problem was most recently seen with package version 1:3.28.0-0ubuntu2, the problem page at https://errors.ubuntu.com/problem/6b1f4dd86167bf5eb53ddca8469b5084208ddd22 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1759468/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1480673] Re: [ELAN 3320KD-3100] Asus T300 CHI bluetooth Touchpad is recognized incorrectly
I can also confirm that all works well with vanilla 18.04. Multitouch, gestures, etc. :) Typing from it now :) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xinput in Ubuntu. https://bugs.launchpad.net/bugs/1480673 Title: [ELAN 3320KD-3100] Asus T300 CHI bluetooth Touchpad is recognized incorrectly Status in libinput: Won't Fix Status in Linux: Unknown Status in xinput package in Ubuntu: Triaged Bug description: Moved the touchscreen issues to bug #1574341 "[Asus T300 CHI] Synaptics Touch Digitizer V04 - no multitouch". The Asus T300 CHI has a touchscreen and a (bluetooth) keyboard/touchpad combo. Both (touchscreen, touchpad) only work like a mouse (moving pointer, left and right click), scrolling, zooming, etc. is not working. the keyboard works fine. relevant content of /proc/bus/input/devices: [...] I: Bus=0003 Vendor=06cb Product=11f0 Version=0111 N: Name="SYNAPTICS Synaptics Touch Digitizer V04" P: Phys=usb-:00:14.0-7/input0 S: Sysfs=/devices/pci:00/:00:14.0/usb1/1-7/1-7:1.0/0003:06CB:11F0.0004/input/input9 U: Uniq= H: Handlers=mouse1 event9 B: PROP=2 B: EV=b B: KEY=400 0 0 0 0 0 B: ABS=2608003 I: Bus=0003 Vendor=06cb Product=11f0 Version=0111 N: Name="SYNAPTICS Synaptics Touch Digitizer V04 Pen" P: Phys=usb-:00:14.0-7/input0 S: Sysfs=/devices/pci:00/:00:14.0/usb1/1-7/1-7:1.0/0003:06CB:11F0.0004/input/input10 U: Uniq= H: Handlers=mouse2 event10 B: PROP=0 B: EV=1b B: KEY=c03 1 0 0 0 0 B: ABS=103 B: MSC=10 [...] I: Bus=0005 Vendor=0b05 Product=8502 Version=0001 N: Name="ASUS T300CHI DOCKING" P: Phys=34:02:86:7b:3b:9d S: Sysfs=/devices/pci:00/:00:14.0/usb1/1-4/1-4:1.0/bluetooth/hci0/hci0:256/0005:0B05:8502.0006/input/input18 U: Uniq=1c:b7:2c:15:94:8b H: Handlers=sysrq kbd mouse3 event17 B: PROP=0 B: EV=12001f B: KEY=20 0 0 2000 40 3 10207 ff9f387ad9405fff febeffdfffef fffe B: REL=303 B: ABS=700 B: MSC=10 B: LED=1f output of xinput --list: ⎡ Virtual core pointerid=2[master pointer (3)] ⎜ ↳ Virtual core XTEST pointer id=4[slave pointer (2)] ⎜ ↳ B16_b_02 USB-PS/2 Optical Mouse id=9[slave pointer (2)] ⎜ ↳ HID 0566:3108 id=11 [slave pointer (2)] ⎜ ↳ SYNAPTICS Synaptics Touch Digitizer V04 Pen id=14 [slave pointer (2)] ⎜ ↳ SYNAPTICS Synaptics Touch Digitizer V04 id=15 [slave pointer (2)] ⎜ ↳ ASUS T300CHI DOCKINGid=18 [slave pointer (2)] ⎣ Virtual core keyboard id=3[master keyboard (2)] ↳ Virtual core XTEST keyboard id=5[slave keyboard (3)] ↳ Power Buttonid=6[slave keyboard (3)] ↳ Video Bus id=7[slave keyboard (3)] ↳ Sleep Buttonid=8[slave keyboard (3)] ↳ HID 0566:3108 id=10 [slave keyboard (3)] ↳ C-Media Electronics Inc. USB Multimedia Audio Deviceid=12 [slave keyboard (3)] ↳ USB2.0 HD UVC WebCamid=13 [slave keyboard (3)] ↳ Asus WMI hotkeysid=16 [slave keyboard (3)] ↳ AT Translated Set 2 keyboardid=17 [slave keyboard (3)] output of synclient is: Couldn't find synaptics properties. No synaptics driver loaded? but I'm unsure if the synaptics driver is the right place to look since basic functionality is working and the "ASUS T300CHI DOCKING" is recognized as "pointer" it seems that the device is recognized by the kernel but only used as a pointing device. I've also attached the xorg.log output of uname -a: Linux xxx 3.19.0-25-generic #26-Ubuntu SMP Fri Jul 24 21:17:31 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux it's a completely fresh install of xubuntu 15.04 with software-updater run once (so no strange hacks or drivers installed) output of lsb_release -rd: Description: Ubuntu 15.04 Release: 15.04 output of apt-cache policy xinput xinput: Installed: 1.6.1-1 Candidate: 1.6.1-1 Version table: *** 1.6.1-1 0 500 http://de.archive.ubuntu.com/ubuntu/ vivid/main amd64 Packages 100 /var/lib/dpkg/status expected results: - scrolling on touchpad and touchscreen should work with a two-finger gesture - zooming on touchpad and touchscreen should work with a two-finger gesture actual results: two fingers are not recognized on touchscreen or touchpad Any help would be appreciated, if you need more console output or logs, please let me know. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: x
[Desktop-packages] [Bug 1767648] Re: Top bar and shell dialogs are not displayed properly when zoom is enabled
I've hit a new problem: During zoom any new actors displayed for the first time (e.g. some bubble menus) are themselves not clones. If you start gnome-shell with zoom already enabled then even major actors like the panel or dash are also not clones. Because the unzoomed version either never existed or was never in a stage at least. So we can't test for them being clones, meaning https://gitlab.gnome.org/GNOME/mutter/merge_requests/52 won't help us here even after fixing the bugs in that branch :( -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1767648 Title: Top bar and shell dialogs are not displayed properly when zoom is enabled Status in Mutter: Confirmed Status in gnome-shell package in Ubuntu: Confirmed Status in mutter package in Ubuntu: In Progress Bug description: When zoom is enabled, the top bar and some shell dialogs (wireless network selection, shutdown dialog, etc.) are not displayed properly. (See the attached screenshots.) Steps to reproduce the issue: 1. Enable Zoom in Setting > Universal Access 2. (Optional) Set zoom factor to around 3 (or higher) 3. Look at the top bar. You will notice that all texts and icons are now gone. If you move your cursor to the right of the top bar, and then click on the status menu, you will see that only a portion of the menu is shown. 4. For the shell dialogs, go to the Settings app. In the Wifi section, choose one of the secured network available. You will see that the password dialog is not displayed in its entirety. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-shell 3.28.1-0ubuntu2 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 CasperVersion: 1.394 CurrentDesktop: ubuntu:GNOME Date: Sat Apr 28 12:54:24 2018 DisplayManager: gdm3 GsettingsChanges: b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'" b'org.gnome.desktop.interface' b'cursor-size' b'96' LiveMediaBuild: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SHELL=/bin/bash SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1767648/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1771785] [NEW] Files doesn't snap to the sides
Public bug reported: With the default Ubuntu install you cannot snap Files to the side of the screen on a 1366x768 screen. An application won't snap if it cannot be resized to half the screen size, and the minimum width of Files is clearly slightly larger than this. Adjusting the minimum width by a few pixels would seem to be the best option (that may be subjective). This may, however, be considered also as a side effect of the Ubuntu Dock down the left hand side, which reduces the effective screen width. An alternative fix is to reduce the icon size of the dock from 48 to 46 as this allows enough width for Files to now snap to the sides. Visually there is little difference, but 48 very much feels the right number (it matches native icon image sizes, etc.), so unless a more drastic change to 32 makes sense, I would suggest the preferred fix is to adjust Nautilus/Files - other docks used on the side would presumably have similar problems with a commonly used size for larger icons. ** Affects: nautilus (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1771785 Title: Files doesn't snap to the sides Status in nautilus package in Ubuntu: New Bug description: With the default Ubuntu install you cannot snap Files to the side of the screen on a 1366x768 screen. An application won't snap if it cannot be resized to half the screen size, and the minimum width of Files is clearly slightly larger than this. Adjusting the minimum width by a few pixels would seem to be the best option (that may be subjective). This may, however, be considered also as a side effect of the Ubuntu Dock down the left hand side, which reduces the effective screen width. An alternative fix is to reduce the icon size of the dock from 48 to 46 as this allows enough width for Files to now snap to the sides. Visually there is little difference, but 48 very much feels the right number (it matches native icon image sizes, etc.), so unless a more drastic change to 32 makes sense, I would suggest the preferred fix is to adjust Nautilus/Files - other docks used on the side would presumably have similar problems with a commonly used size for larger icons. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1771785/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1771787] Re: gnome-control-center crashed with SIGSEGV
*** This bug is a duplicate of bug 1754954 *** https://bugs.launchpad.net/bugs/1754954 ** Information type changed from Private to Public -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1771787 Title: gnome-control-center crashed with SIGSEGV Status in gnome-control-center package in Ubuntu: New Bug description: Ubuntu Budgie 18.04 LTS : gnome-control-center crashed with SIGSEGV ProblemType: Crash DistroRelease: Ubuntu 18.04 Package: gnome-control-center 1:3.28.1-0ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 CasperVersion: 1.394 CurrentDesktop: Budgie:GNOME Date: Thu May 17 09:48:17 2018 ExecutablePath: /usr/bin/gnome-control-center LiveMediaBuild: Ubuntu-Budgie 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) ProcCmdline: gnome-control-center --overview ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SegvAnalysis: Segfault happened at: 0x7f2bc185bc0d:mov0x8(%rdi),%eax PC (0x7f2bc185bc0d) ok source "0x8(%rdi)" (0x0008) not located in a known VMA region (needed readable region)! destination "%eax" ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: gnome-control-center StacktraceTop: ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0 Title: gnome-control-center crashed with SIGSEGV UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1771787/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1771787] Re: gnome-control-center crashed with SIGSEGV
*** This bug is a duplicate of bug 1754954 *** https://bugs.launchpad.net/bugs/1754954 Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #1754954, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find. ** Attachment removed: "CoreDump.gz" https://bugs.launchpad.net/bugs/1771787/+attachment/5140736/+files/CoreDump.gz ** Attachment removed: "Disassembly.txt" https://bugs.launchpad.net/bugs/1771787/+attachment/5140738/+files/Disassembly.txt ** Attachment removed: "ProcMaps.txt" https://bugs.launchpad.net/bugs/1771787/+attachment/5140741/+files/ProcMaps.txt ** Attachment removed: "ProcStatus.txt" https://bugs.launchpad.net/bugs/1771787/+attachment/5140742/+files/ProcStatus.txt ** Attachment removed: "Registers.txt" https://bugs.launchpad.net/bugs/1771787/+attachment/5140743/+files/Registers.txt ** Attachment removed: "Stacktrace.txt" https://bugs.launchpad.net/bugs/1771787/+attachment/5140744/+files/Stacktrace.txt ** Attachment removed: "ThreadStacktrace.txt" https://bugs.launchpad.net/bugs/1771787/+attachment/5140745/+files/ThreadStacktrace.txt ** This bug has been marked a duplicate of private bug 1754954 ** Tags removed: need-amd64-retrace -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1771787 Title: gnome-control-center crashed with SIGSEGV Status in gnome-control-center package in Ubuntu: New Bug description: Ubuntu Budgie 18.04 LTS : gnome-control-center crashed with SIGSEGV ProblemType: Crash DistroRelease: Ubuntu 18.04 Package: gnome-control-center 1:3.28.1-0ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 CasperVersion: 1.394 CurrentDesktop: Budgie:GNOME Date: Thu May 17 09:48:17 2018 ExecutablePath: /usr/bin/gnome-control-center LiveMediaBuild: Ubuntu-Budgie 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) ProcCmdline: gnome-control-center --overview ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SegvAnalysis: Segfault happened at: 0x7f2bc185bc0d:mov0x8(%rdi),%eax PC (0x7f2bc185bc0d) ok source "0x8(%rdi)" (0x0008) not located in a known VMA region (needed readable region)! destination "%eax" ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: gnome-control-center StacktraceTop: ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0 Title: gnome-control-center crashed with SIGSEGV UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1771787/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1771273] Re: Gnome-shell crashes when wake up after updated to 3.28.1-0ubuntu2
Hi Daniel, The problem never appeared after it happened last time. However, I found the crash file for the previous crash, and here they are. Bug #1771788 And there's still another crash, which happened at the same time. However, the owner is gdm, and I can't upload it neither with my permission nor with sudo. How should I do? Btw, you forgot to tell me that I should've commented /etc/apport/crashdb.conf. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1771273 Title: Gnome-shell crashes when wake up after updated to 3.28.1-0ubuntu2 Status in gnome-shell package in Ubuntu: Incomplete Bug description: Hello, After having updated gnome-shell from 3.28.1-0ubuntu1 to 3.28.1-0ubuntu2, I've experienced the gnome-shell crash after every time I wake it up. It seems that it has killed my session. When I wakes my computer up, it shows the very first message usually only appear when starting the computer, like starting the snappy daemon, starting mysql server, etc. I'm using Ubuntu 18.04 LTS, Gnome-shell, Wayland. Please tell me what information I need to provide to confirm this bug. Thanks. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1771273/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1768741] Re: hplip does not wake up printer
This seems to be related to systemd-resolved rather than hplip. I set the printer to static IP and wakeup works fine. Can be closed ** Changed in: hplip (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to hplip in Ubuntu. https://bugs.launchpad.net/bugs/1768741 Title: hplip does not wake up printer Status in hplip package in Ubuntu: Invalid Bug description: Ubuntu 18.04 fresh install Printer: Color Laserjet Pro MFP M477fdw The printer suspends after 5 mins to save power. Expected: A print request should wake the printer and print. Actual: The printer queue goes on hold Mitigation measures: 1) wake printer manually (from the display) + unpause queue -> does not print 2) wake printer manually + restart queue -> does not print 3) restart printer (WHY???) + unpause queue -> PRINTS !!! This behaviour can be reproduced in 18.04 and does not exist in previous versions of Ubuntu ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: hplip 3.17.10+repack0-5 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu May 3 08:30:01 2018 InstallationDate: Installed on 2018-04-30 (2 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) Lpstat: device for HP_Color_LaserJet_MFP_M477fdw: hp:/net/HP_Color_LaserJet_MFP_M477fdw?ip=10.1.0.21 Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 05ac:0273 Apple, Inc. Bus 001 Device 002: ID 05ac:8290 Apple, Inc. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Apple Inc. MacBookPro12,1 Papersize: a4 PpdFiles: Error: command ['fgrep', '-H', '*NickName', '/etc/cups/ppd/HP_Color_LaserJet_MFP_M477fdw.ppd'] failed with exit code 2: grep: /etc/cups/ppd/HP_Color_LaserJet_MFP_M477fdw.ppd: Permission denied ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-20-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1 SourcePackage: hplip UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/08/2017 dmi.bios.vendor: Apple Inc. dmi.bios.version: MBP121.88Z.0171.B00.1708080033 dmi.board.name: Mac-E43C1C25D4880AD6 dmi.board.vendor: Apple Inc. dmi.board.version: MacBookPro12,1 dmi.chassis.type: 9 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-E43C1C25D4880AD6 dmi.modalias: dmi:bvnAppleInc.:bvrMBP121.88Z.0171.B00.1708080033:bd08/08/2017:svnAppleInc.:pnMacBookPro12,1:pvr1.0:rvnAppleInc.:rnMac-E43C1C25D4880AD6:rvrMacBookPro12,1:cvnAppleInc.:ct9:cvrMac-E43C1C25D4880AD6: dmi.product.family: MacBook Pro dmi.product.name: MacBookPro12,1 dmi.product.version: 1.0 dmi.sys.vendor: Apple Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/hplip/+bug/1768741/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1768794] Re: Snap branches all show with same name
Hello Michal, or anyone else affected, Accepted gnome-software into bionic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/gnome- software/3.28.1-0ubuntu4.18.04.1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed.Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested and change the tag from verification-needed-bionic to verification-done-bionic. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-bionic. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance! ** Tags added: verification-needed verification-needed-bionic -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-software in Ubuntu. https://bugs.launchpad.net/bugs/1768794 Title: Snap branches all show with same name Status in gnome-software package in Ubuntu: Fix Released Status in gnome-software source package in Bionic: Fix Committed Status in gnome-software source package in Cosmic: Fix Released Bug description: [Impact] Snaps with multiple branches (e.g. communitheme) all show in GNOME Software with the branches having the same name. Steps to reproduce: 1. Search for ”communitheme” 2. Select ”communitheme” result 3. Click on the channel selection button 4. You will see a popup with loong list of channels Expected result: All branches/channels are shown. Observed result: All branches have the same name. [Regression Potential] Fix was an invalid iterator, unlikely to cause further issues. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1768794/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1768779] Re: Snap channel selection list not scrollable
Hello Michal, or anyone else affected, Accepted gnome-software into bionic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/gnome- software/3.28.1-0ubuntu4.18.04.1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed.Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested and change the tag from verification-needed-bionic to verification-done-bionic. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-bionic. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance! ** Tags added: verification-needed verification-needed-bionic -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-software in Ubuntu. https://bugs.launchpad.net/bugs/1768779 Title: Snap channel selection list not scrollable Status in gnome-software package in Ubuntu: Fix Released Status in gnome-software source package in Xenial: Fix Committed Status in gnome-software source package in Bionic: Fix Committed Status in gnome-software source package in Cosmic: Fix Released Bug description: [Impact] Snaps with many channels/branches (e.g. communitheme) make the channel selector too large - it should use a scrollable window if there are many. [Test Case] 1. Search for ”communitheme” in the store 2. Open ”communitheme” result 3. Click on the channel selection button 4. You will see a popup with loong list of channels 5. Try to scroll to see more entries Expected result: You can scroll the list What happen instead: You cannot scroll the list [Regression Potential] Solution is to use a GtkScrolledWindow for the list. Could cause other UI bugs to occur. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1768779/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1769556] Re: Snap branches shown in random order
Hello Robert, or anyone else affected, Accepted gnome-software into bionic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/gnome- software/3.28.1-0ubuntu4.18.04.1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed.Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested and change the tag from verification-needed-bionic to verification-done-bionic. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-bionic. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance! ** Tags added: verification-needed verification-needed-bionic -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-software in Ubuntu. https://bugs.launchpad.net/bugs/1769556 Title: Snap branches shown in random order Status in gnome-software package in Ubuntu: Fix Released Status in gnome-software source package in Xenial: Fix Committed Status in gnome-software source package in Bionic: Fix Committed Status in gnome-software source package in Cosmic: Fix Released Bug description: [Impact] Snap branches are shown in a random order. [Test Case] 1. Open GNOME Software 2. Search for and select "communitheme" snap 3. Select available channels (requires LP: #1768779 to be fixed). Expected result: Branches are shown in some predictable order. Observed result: Branches are shown in a random order. [Regression Potential] Solution is to sort branches alphabetically, could introduce new bugs in channel code. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1769556/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1767445] Re: Uninstalled snaps show most recent channel version, not version to be installed by default
Hello Adam, or anyone else affected, Accepted gnome-software into bionic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/gnome- software/3.28.1-0ubuntu4.18.04.1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed.Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested and change the tag from verification-needed-bionic to verification-done-bionic. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-bionic. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance! ** Tags added: verification-needed verification-needed-bionic -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-software in Ubuntu. https://bugs.launchpad.net/bugs/1767445 Title: Uninstalled snaps show most recent channel version, not version to be installed by default Status in snapd: New Status in Snap Store: New Status in gnome-software package in Ubuntu: Fix Released Status in gnome-software source package in Xenial: Fix Committed Status in gnome-software source package in Bionic: Fix Committed Status in gnome-software source package in Cosmic: Fix Released Bug description: [Impact] GNOME Software can show incorrect version of snap that will be installed on details page. [Test Case] 1. Open GNOME Software. Ensure blender snap is not installed. 2. Select blender snap (tried 28-04-2018, may change if store versions are changed) Expected result: Version label shows version to be installed (stable channel by default) Observed result: Version label shows most recently uploaded version, i.e. from the edge channel. This is not the version that will be installed when clicking install. [Regression Potential] The logic around choosing which version value to show was changed. Could create other bugs with this data. Orignial text: Ubuntu Software, when showing metadata about a snap package, is most of the time, likely to get information which is misleading, since it shows info from the *most recently* uploaded snap, regardless of which channel the snap was uploaded to. An example of this is to search for blender, and see that the version shows the edge channel - 2.80-4de142e0b7b and not the stable channel - 2.79. After actually installing the application, the correct metadata is shown. See https://forum.snapcraft.io/t/unexpected-revision-information- exposed-in-some-situations/5163 for more details. To manage notifications about this bug go to: https://bugs.launchpad.net/snapd/+bug/1767445/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1766137] Re: [regression] Password accepted but login fails (blank purple screen and mouse pointer only)
** Changed in: gnome-shell (Ubuntu Bionic) Status: Confirmed => Invalid ** Changed in: gnome-shell (Ubuntu) Status: Won't Fix => Invalid ** Changed in: gdm3 (Ubuntu Bionic) Status: Confirmed => In Progress ** Changed in: gdm3 (Ubuntu Bionic) Assignee: (unassigned) => Iain Lane (laney) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1766137 Title: [regression] Password accepted but login fails (blank purple screen and mouse pointer only) Status in gdm: Fix Released Status in Release Notes for Ubuntu: Fix Released Status in gdm3 package in Ubuntu: In Progress Status in gnome-shell package in Ubuntu: Invalid Status in gdm3 source package in Bionic: In Progress Status in gnome-shell source package in Bionic: Invalid Bug description: WORKAROUND: After typing an incorrect password, click Cancel, then click your name, then enter your password again. --- Trying to log into my session (Gnome, Xorg), if I enter the wrong password before entering it correctly, the session doesn't load and I get a purple screen, a mouse cursor, and an invisible but clickable menu in the top right. If I enter it correctly the first time, there is no problem. I've replicated this from a fresh boot, after logging out and after 'sudo service gdm restart' from the Ctrl-Alt-F4 console. This is a fresh install, and didn't occur when I was using a previous install of 18.04 (until Friday). ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gdm3 3.28.0-0ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-15.16-generic 4.15.15 Uname: Linux 4.15.0-15-generic x86_64 ApportVersion: 2.20.9-0ubuntu6 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sun Apr 22 20:31:13 2018 InstallationDate: Installed on 2018-04-22 (0 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180421.1) SourcePackage: gdm3 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/gdm/+bug/1766137/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1766137] Re: [regression] Password accepted but login fails (blank purple screen and mouse pointer only)
** Description changed: - WORKAROUND: After typing an incorrect password, click Cancel, then click - your name, then enter your password again. + [ Description ] + + Due to a refcounting bug, a GDBusConnection was getting disposed when it + was still required. The symptom of this was that you couldn't log in if + you'd got your password wrong. + + [ Test case ] + + 1. Boot to GDM + 2. Click your username + 3. Type the wrong password a couple of times, pressing enter after each time + 4. Type the right password + + If the bug is happening, after 4. the system hangs at a blank screen + with the mouse cursor. If you then switch to a VT or otherwise connect + to the machine, you can examine the journal and you'll see a + G_IS_DBUS_CONNECTION failure. + + [ Fix ] + + Marco and I worked upstream on this fix. We found out that there was a + problem like this- + + The GdmClient has a shared GDBusConnection for its operations. The first + time someone calls for it, it is created and stored in the object's + private structure. Subsequent calls return *a new reference* to this + same object. It turned out that the asynchronous method to get the + connection was accidentally unreferencing its object before giving it to + the caller if it was returning an already-existing connection. + + For this to work properly, we need to nullify the pointer we stored when + the connection goes away, so we know when to make a new one. There were + some cases where we didn't add the weak references required to do that. + Those are also fixed. + + [ Regression potential ] + + Now we share connections more than we did before. We also more carefully + track when to clear our object. If we got this wrong, we might end up + leaking the connection or dropping it in even more cases. + + [ Original report ] + + + WORKAROUND: After typing an incorrect password, click Cancel, then click your name, then enter your password again. --- Trying to log into my session (Gnome, Xorg), if I enter the wrong password before entering it correctly, the session doesn't load and I get a purple screen, a mouse cursor, and an invisible but clickable menu in the top right. If I enter it correctly the first time, there is no problem. I've replicated this from a fresh boot, after logging out and after 'sudo service gdm restart' from the Ctrl-Alt-F4 console. This is a fresh install, and didn't occur when I was using a previous install of 18.04 (until Friday). ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gdm3 3.28.0-0ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-15.16-generic 4.15.15 Uname: Linux 4.15.0-15-generic x86_64 ApportVersion: 2.20.9-0ubuntu6 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sun Apr 22 20:31:13 2018 InstallationDate: Installed on 2018-04-22 (0 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180421.1) SourcePackage: gdm3 UpgradeStatus: No upgrade log present (probably fresh install) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1766137 Title: [regression] Password accepted but login fails (blank purple screen and mouse pointer only) Status in gdm: Fix Released Status in Release Notes for Ubuntu: Fix Released Status in gdm3 package in Ubuntu: In Progress Status in gnome-shell package in Ubuntu: Invalid Status in gdm3 source package in Bionic: In Progress Status in gnome-shell source package in Bionic: Invalid Bug description: [ Description ] Due to a refcounting bug, a GDBusConnection was getting disposed when it was still required. The symptom of this was that you couldn't log in if you'd got your password wrong. [ Test case ] 1. Boot to GDM 2. Click your username 3. Type the wrong password a couple of times, pressing enter after each time 4. Type the right password If the bug is happening, after 4. the system hangs at a blank screen with the mouse cursor. If you then switch to a VT or otherwise connect to the machine, you can examine the journal and you'll see a G_IS_DBUS_CONNECTION failure. [ Fix ] Marco and I worked upstream on this fix. We found out that there was a problem like this- The GdmClient has a shared GDBusConnection for its operations. The first time someone calls for it, it is created and stored in the object's private structure. Subsequent calls return *a new reference* to this same object. It turned out that the asynchronous method to get the connection was accidentally unreferencing its object before giving it to the caller if it was returning an already-existing connection. For this to work properly, we need to nullify the pointer we stored when the connection goes away, so we know when to make a new one. There were some cases where we didn't add the weak references required to do that. Those are also fixed.
[Desktop-packages] [Bug 1728012] Re: Many 3rd party scanner drivers are broken by a sane change
Brother MFC-J480DW, printer ok, scanner doesn't work in Ubuntu 18.04, fresh installation yesterday. I use simple scan, scanner is not found. Scanner works fine with 16.04. In brother folder, brscan4-04.4-3.amd64.deb, libsane-common version 1.0.27-1 experimental3ubuntu 2. If you find the way to solve this problem -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to sane-backends in Ubuntu. https://bugs.launchpad.net/bugs/1728012 Title: Many 3rd party scanner drivers are broken by a sane change Status in sane-backends package in Ubuntu: Confirmed Bug description: Many scanners can no more be used since sane has changed something: The 3rd-party plug-in the vendor provides as .deb package will still install. But the scanner is no more recognized. Scanners that are affected are(besides others): - Epson Perfection V10 - Epson Perfection V1000 - Epson WorkForce GT-1500 - Brother MFC-8510DN - Epson Perfection V33 It is to note that the probability that the scanner manufacturers fix things others broke is below 100%. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: libsane1 1.0.27-1~experimental2ubuntu2 Uname: Linux 4.14.0-041400rc5-lowlatency x86_64 ApportVersion: 2.20.7-0ubuntu3.1 Architecture: amd64 Date: Fri Oct 27 12:35:52 2017 EcryptfsInUse: Yes SourcePackage: sane-backends UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sane-backends/+bug/1728012/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1771797] [NEW] Massive performance regressions and faulty rendering.
Public bug reported: With the Firefox 60 upgrade, Firefox renders text improperly, to the extent that text is sometimes unreadable. Videos can no longer be viewed in full screen without lots of skipped frames. I've never had any of these issues with previous versions. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: firefox 60.0+build2-0ubuntu0.14.04.1 ProcVersionSignature: Ubuntu 4.4.0-124.148~14.04.1-generic 4.4.117 Uname: Linux 4.4.0-124-generic x86_64 AddonCompatCheckDisabled: False ApportVersion: 2.14.1-0ubuntu3.27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jo-erlend 2735 F pulseaudio BuildID: 20180509235355 Channel: Unavailable CurrentDesktop: Unity Date: Thu May 17 12:50:30 2018 Extensions: extensions.sqlite corrupt or missing ForcedLayersAccel: False IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback IncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) InstallationDate: Installed on 2017-01-25 (477 days ago) InstallationMedia: Ubuntu 14.04.5 LTS "Trusty Tahr" - Release amd64 (20160803) IpRoute: default via 192.168.0.1 dev eth0 proto static 192.168.0.0/24 dev eth0 proto kernel scope link src 192.168.0.105 metric 1 192.168.0.0/24 dev wlan0 proto kernel scope link src 192.168.0.102 metric 9 192.168.122.0/24 dev virbr0 proto kernel scope link src 192.168.122.1 Locales: extensions.sqlite corrupt or missing Plugins: Shockwave Flash - /usr/lib/flashplugin-installer/libflashplayer.so PrefSources: prefs.js Profiles: Profile0 (Default) - LastVersion=60.0/20180509235355 (In use) RunningIncompatibleAddons: False SourcePackage: firefox Themes: extensions.sqlite corrupt or missing UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/18/2016 dmi.bios.vendor: LENOVO dmi.bios.version: D7CN30WW(V3.03) dmi.board.asset.tag: NO Asset Tag dmi.board.name: Lenovo E51-80 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40705 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo E51-80 dmi.modalias: dmi:bvnLENOVO:bvrD7CN30WW(V3.03):bd04/18/2016:svnLENOVO:pn80QB:pvrLenovoE51-80:rvnLENOVO:rnLenovoE51-80:rvrSDK0J40705WIN:cvnLENOVO:ct10:cvrLenovoE51-80: dmi.product.name: 80QB dmi.product.version: Lenovo E51-80 dmi.sys.vendor: LENOVO ** Affects: firefox (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug third-party-packages trusty -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/1771797 Title: Massive performance regressions and faulty rendering. Status in firefox package in Ubuntu: New Bug description: With the Firefox 60 upgrade, Firefox renders text improperly, to the extent that text is sometimes unreadable. Videos can no longer be viewed in full screen without lots of skipped frames. I've never had any of these issues with previous versions. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: firefox 60.0+build2-0ubuntu0.14.04.1 ProcVersionSignature: Ubuntu 4.4.0-124.148~14.04.1-generic 4.4.117 Uname: Linux 4.4.0-124-generic x86_64 AddonCompatCheckDisabled: False ApportVersion: 2.14.1-0ubuntu3.27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jo-erlend 2735 F pulseaudio BuildID: 20180509235355 Channel: Unavailable CurrentDesktop: Unity Date: Thu May 17 12:50:30 2018 Extensions: extensions.sqlite corrupt or missing ForcedLayersAccel: False IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback IncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) InstallationDate: Installed on 2017-01-25 (477 days ago) InstallationMedia: Ubuntu 14.04.5 LTS "Trusty Tahr" - Release amd64 (20160803) IpRoute: default via 192.168.0.1 dev eth0 proto static 192.168.0.0/24 dev eth0 proto kernel scope link src 192.168.0.105 metric 1 192.168.0.0/24 dev wlan0 proto kernel scope link src 192.168.0.102 metric 9 192.168.122.0/24 dev virbr0 proto kernel scope link src 192.168.122.1 Locales: extensions.sqlite corrupt or missing Plugins: Shockwave Flash - /usr/lib/flashplugin-installer/libflashplayer.so PrefSources: prefs.js Profiles: Profile0 (Default) - LastVersion=60.0/20180509235355 (In use) RunningIncompatibleAddons: False SourcePackage: firefox Themes: extensions.sqlite corrupt or missing UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/18/2016 dmi.bios.vendor: LENOVO dmi.bios.version: D7CN30WW(V3.03) dmi.board.asset.tag: NO Asset Tag dmi.board.name: Lenovo E51-80 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40705 WIN dmi.chassis.asset.
[Desktop-packages] [Bug 1766137] Re: [regression] Password accepted but login fails (blank purple screen and mouse pointer only)
** Branch linked: lp:~ubuntu-desktop/gdm/ubuntu -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1766137 Title: [regression] Password accepted but login fails (blank purple screen and mouse pointer only) Status in gdm: Fix Released Status in Release Notes for Ubuntu: Fix Released Status in gdm3 package in Ubuntu: In Progress Status in gnome-shell package in Ubuntu: Invalid Status in gdm3 source package in Bionic: In Progress Status in gnome-shell source package in Bionic: Invalid Bug description: [ Description ] Due to a refcounting bug, a GDBusConnection was getting disposed when it was still required. The symptom of this was that you couldn't log in if you'd got your password wrong. [ Test case ] 1. Boot to GDM 2. Click your username 3. Type the wrong password a couple of times, pressing enter after each time 4. Type the right password If the bug is happening, after 4. the system hangs at a blank screen with the mouse cursor. If you then switch to a VT or otherwise connect to the machine, you can examine the journal and you'll see a G_IS_DBUS_CONNECTION failure. [ Fix ] Marco and I worked upstream on this fix. We found out that there was a problem like this- The GdmClient has a shared GDBusConnection for its operations. The first time someone calls for it, it is created and stored in the object's private structure. Subsequent calls return *a new reference* to this same object. It turned out that the asynchronous method to get the connection was accidentally unreferencing its object before giving it to the caller if it was returning an already-existing connection. For this to work properly, we need to nullify the pointer we stored when the connection goes away, so we know when to make a new one. There were some cases where we didn't add the weak references required to do that. Those are also fixed. [ Regression potential ] Now we share connections more than we did before. We also more carefully track when to clear our object. If we got this wrong, we might end up leaking the connection or dropping it in even more cases. [ Original report ] WORKAROUND: After typing an incorrect password, click Cancel, then click your name, then enter your password again. --- Trying to log into my session (Gnome, Xorg), if I enter the wrong password before entering it correctly, the session doesn't load and I get a purple screen, a mouse cursor, and an invisible but clickable menu in the top right. If I enter it correctly the first time, there is no problem. I've replicated this from a fresh boot, after logging out and after 'sudo service gdm restart' from the Ctrl-Alt-F4 console. This is a fresh install, and didn't occur when I was using a previous install of 18.04 (until Friday). ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gdm3 3.28.0-0ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-15.16-generic 4.15.15 Uname: Linux 4.15.0-15-generic x86_64 ApportVersion: 2.20.9-0ubuntu6 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sun Apr 22 20:31:13 2018 InstallationDate: Installed on 2018-04-22 (0 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180421.1) SourcePackage: gdm3 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/gdm/+bug/1766137/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1379531] Re: "Combine sides" should be "combine pages"?
What is the actual outcome of "combine sides", is this a print related thing to print side by side or what? I'm still struggling to figure out what this actually does. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to simple-scan in Ubuntu. https://bugs.launchpad.net/bugs/1379531 Title: "Combine sides" should be "combine pages"? Status in Ubuntu Translations: Invalid Status in simple-scan package in Ubuntu: New Bug description: Combine sides and Combine sides (reverse) look like a German speaker with poor English mistranslated 'Seiten' as 'sides' rather than 'pages'? Located in ../src/ui.vala:1204 Located in ../src/ui.vala:1214 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-translations/+bug/1379531/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1768794] Re: Snap branches all show with same name
FWIW there's a bug store-side, as it shouldn't be exposing branches at all. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-software in Ubuntu. https://bugs.launchpad.net/bugs/1768794 Title: Snap branches all show with same name Status in gnome-software package in Ubuntu: Fix Released Status in gnome-software source package in Bionic: Fix Committed Status in gnome-software source package in Cosmic: Fix Released Bug description: [Impact] Snaps with multiple branches (e.g. communitheme) all show in GNOME Software with the branches having the same name. Steps to reproduce: 1. Search for ”communitheme” 2. Select ”communitheme” result 3. Click on the channel selection button 4. You will see a popup with loong list of channels Expected result: All branches/channels are shown. Observed result: All branches have the same name. [Regression Potential] Fix was an invalid iterator, unlikely to cause further issues. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1768794/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1766137] Re: [regression] Password accepted but login fails (blank purple screen and mouse pointer only)
Packages coming your way soon. They work for me/us, but please give confirmation/denial. There will be a message when they're accepted into bionic for testing. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1766137 Title: [regression] Password accepted but login fails (blank purple screen and mouse pointer only) Status in gdm: Fix Released Status in Release Notes for Ubuntu: Fix Released Status in gdm3 package in Ubuntu: In Progress Status in gnome-shell package in Ubuntu: Invalid Status in gdm3 source package in Bionic: In Progress Status in gnome-shell source package in Bionic: Invalid Bug description: [ Description ] Due to a refcounting bug, a GDBusConnection was getting disposed when it was still required. The symptom of this was that you couldn't log in if you'd got your password wrong. [ Test case ] 1. Boot to GDM 2. Click your username 3. Type the wrong password a couple of times, pressing enter after each time 4. Type the right password If the bug is happening, after 4. the system hangs at a blank screen with the mouse cursor. If you then switch to a VT or otherwise connect to the machine, you can examine the journal and you'll see a G_IS_DBUS_CONNECTION failure. [ Fix ] Marco and I worked upstream on this fix. We found out that there was a problem like this- The GdmClient has a shared GDBusConnection for its operations. The first time someone calls for it, it is created and stored in the object's private structure. Subsequent calls return *a new reference* to this same object. It turned out that the asynchronous method to get the connection was accidentally unreferencing its object before giving it to the caller if it was returning an already-existing connection. For this to work properly, we need to nullify the pointer we stored when the connection goes away, so we know when to make a new one. There were some cases where we didn't add the weak references required to do that. Those are also fixed. [ Regression potential ] Now we share connections more than we did before. We also more carefully track when to clear our object. If we got this wrong, we might end up leaking the connection or dropping it in even more cases. [ Original report ] WORKAROUND: After typing an incorrect password, click Cancel, then click your name, then enter your password again. --- Trying to log into my session (Gnome, Xorg), if I enter the wrong password before entering it correctly, the session doesn't load and I get a purple screen, a mouse cursor, and an invisible but clickable menu in the top right. If I enter it correctly the first time, there is no problem. I've replicated this from a fresh boot, after logging out and after 'sudo service gdm restart' from the Ctrl-Alt-F4 console. This is a fresh install, and didn't occur when I was using a previous install of 18.04 (until Friday). ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gdm3 3.28.0-0ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-15.16-generic 4.15.15 Uname: Linux 4.15.0-15-generic x86_64 ApportVersion: 2.20.9-0ubuntu6 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sun Apr 22 20:31:13 2018 InstallationDate: Installed on 2018-04-22 (0 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180421.1) SourcePackage: gdm3 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/gdm/+bug/1766137/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 375396] Re: ubuntu patch 01_paging.dpatch breaks rdesktop's seamlessrdp
Tried 1.8.3 from linux Mint 18.3 repository. Same problem as described previously. All windows and menus have windows decorations. Impossible to use -A and -D options simultaneously. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to rdesktop in Ubuntu. https://bugs.launchpad.net/bugs/375396 Title: ubuntu patch 01_paging.dpatch breaks rdesktop's seamlessrdp Status in rdesktop package in Ubuntu: Confirmed Bug description: Binary package hint: rdesktop in package rdesktop there is a custom ubuntu patch called 01_paging.dpatch - " Add viewport mode , suitable for small screens." I don't know what this patch does but is it causes seamlessrdp to stop working "seamless" - meaning the window manager decoration and "frame" is drawn in addition to the native windows application window the way it's supposed to be is without the WM decoration as if no WM is running , but only the windows app window :) for more information on seamlessrdp : http://www.cendio.com/seamlessrdp/ Thanks. Description:Ubuntu 9.04 Release:9.04 rdesktop: Installed: 1.6.0-2ubuntu1 Candidate: 1.6.0-2ubuntu1 Version table: 1.6.0-2ubuntu1 0 500 http://archive.ubuntu.com jaunty/main Packages *** 1.6.0-2ubuntu1 0 100 /var/lib/dpkg/status To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rdesktop/+bug/375396/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1768794] Re: Snap branches all show with same name
OTOH what the client should be doing is looking at 'tracks' to get the order of the channels, and then using that to look up each track in the map; this would've avoided the issue (but not the info leak which is still a bug) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-software in Ubuntu. https://bugs.launchpad.net/bugs/1768794 Title: Snap branches all show with same name Status in gnome-software package in Ubuntu: Fix Released Status in gnome-software source package in Bionic: Fix Committed Status in gnome-software source package in Cosmic: Fix Released Bug description: [Impact] Snaps with multiple branches (e.g. communitheme) all show in GNOME Software with the branches having the same name. Steps to reproduce: 1. Search for ”communitheme” 2. Select ”communitheme” result 3. Click on the channel selection button 4. You will see a popup with loong list of channels Expected result: All branches/channels are shown. Observed result: All branches have the same name. [Regression Potential] Fix was an invalid iterator, unlikely to cause further issues. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1768794/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1711337] Re: Firefox crashes at start on armv7L after 55.0.1 update
firefox 60.0+build2-0ubuntu1 is launching for me without crashing (on ubuntu-mate 18.04 on rasberrypi 2B). I have not made any other changes. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/1711337 Title: Firefox crashes at start on armv7L after 55.0.1 update Status in Mozilla Firefox: Expired Status in firefox package in Ubuntu: Confirmed Bug description: Firefox always crashes when launched after the 55.0.1 update on an Orange Pi PC Plus (a single-board computer similar to a Raspberry Pi), even in safe mode. I did a fresh install of Armbian (a Ubuntu Xenial 16.04 re-spin for ARM single-board computer) on a similar board (Orange Pi Plus 2e), installed Firefox and experienced the same problem--it won't load without crashing. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: firefox 55.0.1+build2-0ubuntu0.16.04.2 Uname: Linux 3.4.113-sun8i armv7l AddonCompatCheckDisabled: False AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.25. ApportVersion: 2.20.1-0ubuntu2.10 Architecture: armhf AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: jim1138 F pulseaudio /dev/snd/controlC0: jim1138 F pulseaudio BuildID: 20170814194718 Card0.Amixer.info: Card hw:0 'audiocodec'/'audiocodec' Mixer name : '' Components : '' Controls : 12 Simple ctrls : 12 Card1.Amixer.info: Card hw:1 'sndhdmi'/'sndhdmi' Mixer name : '' Components : '' Controls : 1 Simple ctrls : 1 Card1.Amixer.values: Simple mixer control 'hdmi audio format Function',0 Capabilities: enum Items: 'null' 'pcm' 'AC3' 'MPEG1' 'MP3' 'MPEG2' 'AAC' 'DTS' 'ATRAC' 'ONE_BIT_AUDIO' 'DOLBY_DIGITAL_PLUS' 'DTS_HD' 'MAT' 'WMAPRO' Item0: 'pcm' Channel: Unavailable CurrentDesktop: XFCE Date: Thu Aug 17 05:37:00 2017 Extensions: extensions.sqlite corrupt or missing ForcedLayersAccel: False IncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) IpRoute: default via 192.168.10.1 dev eth0 default via 192.168.10.1 dev wlan0 proto static metric 600 169.254.0.0/16 dev eth0 scope link metric 1000 192.168.10.0/24 dev eth0 proto kernel scope link src 192.168.10.107 192.168.10.0/24 dev wlan0 proto kernel scope link src 192.168.10.108 metric 600 Locales: extensions.sqlite corrupt or missing PciMultimedia: PciNetwork: Profiles: Profile0 (Default) - LastVersion=55.0.1/20170814194718 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no RunningIncompatibleAddons: False SourcePackage: firefox Themes: extensions.sqlite corrupt or missing UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/1711337/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1750533] Re: Proprietary software is labelled red
Hmm, I thought that, at the very least, in GNU/Linux distributions the assumption is that free software is preferred (if not hidden in the way that the FSF would prefer)? Presumably there's a reason why upstream GNOME assigns these colours? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-software in Ubuntu. https://bugs.launchpad.net/bugs/1750533 Title: Proprietary software is labelled red Status in gnome-software package in Ubuntu: Fix Released Bug description: Proprietary software delivered as snaps in GNOME Software is highlighted red in the software details. While it's great that we show the license for software, it's not ideal that the implication of the colours is that free=good, proprietary=bad. We should provide software and enable users to make an informed choice what they install, but not make the implication that it's a bad choice. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1750533/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1771809] [NEW] package bbswitch-dkms (not installed) failed to install/upgrade: installed bbswitch-dkms package post-installation script subprocess returned error exit status 6
Public bug reported: - ProblemType: Package DistroRelease: Ubuntu 18.04 Package: bbswitch-dkms (not installed) ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 Date: Thu May 17 13:13:16 2018 ErrorMessage: installed bbswitch-dkms package post-installation script subprocess returned error exit status 6 InstallationDate: Installed on 2018-05-11 (5 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3 PythonDetails: /root/Error: command ['which', 'python'] failed with exit code 1:, Error: [Errno 2] Adresář nebo soubor neexistuje: "/root/Error: command ['which', 'python'] failed with exit code 1:": "/root/Error: command ['which', 'python'] failed with exit code 1:", unpackaged RelatedPackageVersions: dpkg 1.19.0.5ubuntu2 apt 1.6.1 SourcePackage: bbswitch Title: package bbswitch-dkms (not installed) failed to install/upgrade: installed bbswitch-dkms package post-installation script subprocess returned error exit status 6 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: bbswitch (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package bionic -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to bbswitch in Ubuntu. https://bugs.launchpad.net/bugs/1771809 Title: package bbswitch-dkms (not installed) failed to install/upgrade: installed bbswitch-dkms package post-installation script subprocess returned error exit status 6 Status in bbswitch package in Ubuntu: New Bug description: - ProblemType: Package DistroRelease: Ubuntu 18.04 Package: bbswitch-dkms (not installed) ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 Date: Thu May 17 13:13:16 2018 ErrorMessage: installed bbswitch-dkms package post-installation script subprocess returned error exit status 6 InstallationDate: Installed on 2018-05-11 (5 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3 PythonDetails: /root/Error: command ['which', 'python'] failed with exit code 1:, Error: [Errno 2] Adresář nebo soubor neexistuje: "/root/Error: command ['which', 'python'] failed with exit code 1:": "/root/Error: command ['which', 'python'] failed with exit code 1:", unpackaged RelatedPackageVersions: dpkg 1.19.0.5ubuntu2 apt 1.6.1 SourcePackage: bbswitch Title: package bbswitch-dkms (not installed) failed to install/upgrade: installed bbswitch-dkms package post-installation script subprocess returned error exit status 6 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bbswitch/+bug/1771809/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1652613] Re: package nvidia-340 340.98-0ubuntu0.16.04.1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 6
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: nvidia-graphics-drivers-340 (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-graphics-drivers-340 in Ubuntu. https://bugs.launchpad.net/bugs/1652613 Title: package nvidia-340 340.98-0ubuntu0.16.04.1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 6 Status in nvidia-graphics-drivers-340 package in Ubuntu: Confirmed Bug description: cant istall ubuntu, and windows on my computer. only windows7 enterpries 64bit eng version works. any other version fail to install, at windows install crashed at 2%.. ubuntu drop this fail now, and when i try to install after boot, then dropped a boot sec fail or something. sorry for bad english. i hope u can help me, im waiting for your answer. Thanks for your help, Mark ProblemType: Package DistroRelease: Ubuntu 16.04 Package: nvidia-340 340.98-0ubuntu0.16.04.1 ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13 Uname: Linux 4.4.0-31-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 CasperVersion: 1.376 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true Date: Mon Dec 26 13:30:16 2016 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu DkmsStatus: bbswitch, 0.8, 4.4.0-31-generic, x86_64: built nvidia-340, 340.98, 4.4.0-31-generic, x86_64: built ErrorMessage: subprocess installed post-installation script returned error exit status 6 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:064b] 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] LiveMediaBuild: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) MachineType: Acer Aspire E1-571G ProcKernelCmdLine: file=/cdrom/preseed/hostname.seed boot=casper only-ubiquity cdrom-detect/try-usb=true noprompt floppy.allowed_drive_mask=0 ignore_uuid initrd=/casper/initrd.lz quiet splash --- BOOT_IMAGE=/casper/vmlinuz.efi RelatedPackageVersions: dpkg 1.18.4ubuntu1.1 apt 1.2.12~ubuntu16.04.1 SourcePackage: nvidia-graphics-drivers-340 Title: package nvidia-340 340.98-0ubuntu0.16.04.1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 6 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/11/2013 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V2.15 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: EA50_HC_CR dmi.board.vendor: Acer dmi.board.version: Type2 - Board Version dmi.chassis.type: 10 dmi.chassis.vendor: Insyde Corp. dmi.chassis.version: V2.15 dmi.modalias: dmi:bvnInsydeCorp.:bvrV2.15:bd03/11/2013:svnAcer:pnAspireE1-571G:pvrV2.15:rvnAcer:rnEA50_HC_CR:rvrType2-BoardVersion:cvnInsydeCorp.:ct10:cvrV2.15: dmi.product.name: Aspire E1-571G dmi.product.version: V2.15 dmi.sys.vendor: Acer version.compiz: compiz 1:0.9.12.2+16.04.20160714-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.67-1ubuntu0.16.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu2 version.xserver-xorg-core: xserver-xorg-core 2:1.18.3-1ubuntu2.2 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 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2 xserver.bootTime: Mon Dec 26 13:26:34 2016 xserver.configfile: default xserver.errors: Failed to load module "nvidia" (module does not exist, 0) Failed to load module "nvidia" (module does not exist, 0) NOUVEAU(G0): [XvMC] Failed to initialize extension. xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id8940 vendor AUO xserver.version: 2:1.18.3-1ubuntu2.2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-340/+bug/1652613/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launch
[Desktop-packages] [Bug 1768794] Re: Snap branches all show with same name
The bug has been fixed and the server no longer advertises branches. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-software in Ubuntu. https://bugs.launchpad.net/bugs/1768794 Title: Snap branches all show with same name Status in gnome-software package in Ubuntu: Fix Released Status in gnome-software source package in Bionic: Fix Committed Status in gnome-software source package in Cosmic: Fix Released Bug description: [Impact] Snaps with multiple branches (e.g. communitheme) all show in GNOME Software with the branches having the same name. Steps to reproduce: 1. Search for ”communitheme” 2. Select ”communitheme” result 3. Click on the channel selection button 4. You will see a popup with loong list of channels Expected result: All branches/channels are shown. Observed result: All branches have the same name. [Regression Potential] Fix was an invalid iterator, unlikely to cause further issues. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1768794/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1763918] Re: Xorg crashed with SIGSEGV in GetBarrierDevice()
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: nvidia-graphics-drivers (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-graphics-drivers in Ubuntu. https://bugs.launchpad.net/bugs/1763918 Title: Xorg crashed with SIGSEGV in GetBarrierDevice() Status in nvidia-graphics-drivers package in Ubuntu: Confirmed Bug description: i work in gedit...! ProblemType: Crash DistroRelease: Ubuntu 18.04 Package: xserver-xorg-core 2:1.19.6-1ubuntu3 ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10 Uname: Linux 4.15.0-13-generic x86_64 NonfreeKernelModules: nvidia_modeset 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 390.48 Thu Mar 22 00:42:57 PDT 2018 GCC version: gcc version 7.3.0 (Ubuntu 7.3.0-15ubuntu2) .proc.driver.nvidia.warnings.fbdev: Your system is not currently configured to drive a VGA console on the primary VGA device. The NVIDIA Linux graphics driver requires the use of a text-mode VGA console. Use of other console drivers including, but not limited to, vesafb, may result in corruption and stability problems, and is not supported. ApportVersion: 2.20.9-0ubuntu4 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CrashCounter: 1 Date: Sat Apr 14 14:37:05 2018 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu DkmsStatus: nvidia, 390.48, 4.15.0-13-generic, x86_64: installed nvidia, 390.48, 4.15.0-15-generic, x86_64: installed virtualbox, 5.2.8, 4.15.0-13-generic, x86_64: installed virtualbox, 5.2.8, 4.15.0-15-generic, x86_64: installed ExecutablePath: /usr/lib/xorg/Xorg GraphicsCard: NVIDIA Corporation GP107 [GeForce GTX 1050 Ti] [10de:1c82] (rev a1) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. GP107 [GeForce GTX 1050 Ti] [1043:85cd] InstallationDate: Installed on 2017-09-02 (224 days ago) InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Release amd64 (20170412) MachineType: System manufacturer System Product Name ProcCmdline: /usr/lib/xorg/Xorg vt2 -displayfd 3 -auth /run/user/1000/gdm/Xauthority -background none -noreset -keeptty -verbose 3 ProcEnviron: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-13-generic.efi.signed root=UUID=a5d262b4-1b0f-4856-9935-f6a7f6d6d406 ro quiet splash vt.handoff=1 SegvAnalysis: Segfault happened at: 0x5650239f51fc:cmp0x10(%rax),%esi PC (0x5650239f51fc) ok source "0x10(%rax)" (0x1022af410) not located in a known VMA region (needed readable region)! destination "%esi" ok Stack memory exhausted (SP below stack segment) SegvReason: reading unknown VMA Signal: 11 SourcePackage: nvidia-graphics-drivers StacktraceTop: ?? () miPointerSetPosition () ?? () ?? () GetPointerEvents () Title: Xorg crashed with SIGSEGV in miPointerSetPosition() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip libvirt lpadmin plugdev sambashare sudo dmi.bios.date: 09/19/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2003 dmi.board.asset.tag: Default string dmi.board.name: Z170-P dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2003:bd09/19/2016:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnZ170-P:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.91-2 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.0~rc5-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.0~rc5-1ubuntu1 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers/+bug/1763918/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubsc
[Desktop-packages] [Bug 1771812] [NEW] Software isn't displaying the version of the currently selected snap track
Public bug reported: https://forum.snapcraft.io/t/gnome-software-plugin-snap-source-for- searches/5392 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-software 3.28.1-0ubuntu4 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 CurrentDesktop: communitheme:ubuntu:GNOME Date: Thu May 17 14:02:32 2018 InstallationDate: Installed on 2017-08-03 (286 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) InstalledPlugins: gnome-software-plugin-flatpak 3.28.1-0ubuntu4 gnome-software-plugin-limba N/A gnome-software-plugin-snap3.28.1-0ubuntu4 SourcePackage: gnome-software UpgradeStatus: Upgraded to bionic on 2018-04-22 (25 days ago) ** Affects: gnome-software (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic wayland-session ** Attachment added: "74f17ae332ae7d6ead9c4e41cb7afe4630837c03.jpg" https://bugs.launchpad.net/bugs/1771812/+attachment/5140819/+files/74f17ae332ae7d6ead9c4e41cb7afe4630837c03.jpg -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-software in Ubuntu. https://bugs.launchpad.net/bugs/1771812 Title: Software isn't displaying the version of the currently selected snap track Status in gnome-software package in Ubuntu: New Bug description: https://forum.snapcraft.io/t/gnome-software-plugin-snap-source-for- searches/5392 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-software 3.28.1-0ubuntu4 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 CurrentDesktop: communitheme:ubuntu:GNOME Date: Thu May 17 14:02:32 2018 InstallationDate: Installed on 2017-08-03 (286 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) InstalledPlugins: gnome-software-plugin-flatpak 3.28.1-0ubuntu4 gnome-software-plugin-limba N/A gnome-software-plugin-snap3.28.1-0ubuntu4 SourcePackage: gnome-software UpgradeStatus: Upgraded to bionic on 2018-04-22 (25 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1771812/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1771484] Re: Xorg crashed with SIGABRT in OsAbort() from AbortServer() from FatalError() from message_filter() from dbus_connection_dispatch()
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: xorg-server (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1771484 Title: Xorg crashed with SIGABRT in OsAbort() from AbortServer() from FatalError() from message_filter() from dbus_connection_dispatch() Status in xorg-server package in Ubuntu: Confirmed Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding xorg-server. This problem was most recently seen with package version 2:1.19.6-1ubuntu4, the problem page at https://errors.ubuntu.com/problem/dc5f0fb8ff236a0205b84bdd7b3990b63af2cb33 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1771484/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1543192] Re: Xorg crashed with SIGABRT in OsAbort() from AbortServer() from FatalError() from dix_main() ["no screens found"]
https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1770238?comments=all I ran into the no screens bug. Logging in resulted in a black screen for many minutes after which the login screen reappeared and I am able to login fine. A systemd watchdog kicks in during the many minutes to restart systemd-logind. I don't know why the 2nd login attempt works when the first failed. I can restart systemd-logind after the first login but before the watchdog to speed up the process but if I restart systemd-logind before the first login it doesn't help... May 9 11:04:06 jcormier-MS-7A93 /usr/lib/gdm3/gdm-x-session[2581]: (EE) Screen(s) found, but none have a usable configuration. May 9 11:04:06 jcormier-MS-7A93 /usr/lib/gdm3/gdm-x-session[2581]: (EE) May 9 11:04:06 jcormier-MS-7A93 /usr/lib/gdm3/gdm-x-session[2581]: Fatal server error: May 9 11:04:06 jcormier-MS-7A93 /usr/lib/gdm3/gdm-x-session[2581]: (EE) no screens found(EE) I had caused this by disabling wayland in /etc/gdm3/custom.conf. Re- enabling wayland removed this problem but I am still seeing various other X related issues which cause gnome to kick me back to login screen or reset the computer. :( -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1543192 Title: Xorg crashed with SIGABRT in OsAbort() from AbortServer() from FatalError() from dix_main() ["no screens found"] Status in xorg-server package in Ubuntu: Confirmed Bug description: https://errors.ubuntu.com/problem/4de849dfec89af168af9cda3318221a2a654e530 --- No idea what happened. ProblemType: Crash DistroRelease: Ubuntu 16.04 Package: xserver-xorg-core 2:1.17.3-2ubuntu2 ProcVersionSignature: Ubuntu 4.4.0-2.16-generic 4.4.0 Uname: Linux 4.4.0-2-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.19.4-0ubuntu2 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 CrashCounter: 1 Date: Mon Feb 8 17:07:23 2016 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu ExecutablePath: /usr/lib/xorg/Xorg ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0126] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Lenovo 2nd Generation Core Processor Family Integrated Graphics Controller [17aa:21da] InstallationDate: Installed on 2015-04-30 (283 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) MachineType: LENOVO 429149G ProcCmdline: /usr/lib/xorg/Xorg -core :0 -seat seat0 -auth /var/run/lightdm/root/:0 -nolisten tcp vt7 -novtswitch ProcEnviron: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-2-generic root=UUID=457973fc-512e-4b6a-b65b-85f15fa85b7b ro console=tty1 console=ttyS0 panic=-1 Signal: 6 SourcePackage: xorg-server StacktraceTop: OsAbort () ?? () FatalError () ?? () __libc_start_main (main=0x557f8180ff00, argc=11, argv=0x7fffc9e34fd8, init=, fini=, rtld_fini=, stack_end=0x7fffc9e34fc8) at libc-start.c:289 SystemImageInfo: Error: command ['system-image-cli', '-i'] failed with exit code 2: Title: Xorg crashed with SIGABRT in OsAbort() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: dmi.bios.date: 05/18/2011 dmi.bios.vendor: LENOVO dmi.bios.version: 8DET46WW (1.16 ) dmi.board.asset.tag: Not Available dmi.board.name: 429149G dmi.board.vendor: LENOVO dmi.board.version: Not Available dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvr8DET46WW(1.16):bd05/18/2011:svnLENOVO:pn429149G:pvrThinkPadX220:rvnLENOVO:rn429149G:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 429149G dmi.product.version: ThinkPad X220 dmi.sys.vendor: LENOVO version.compiz: compiz 1:0.9.12.2+16.04.20151211-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.66-2 version.libgl1-mesa-dri: libgl1-mesa-dri 11.1.1-1ubuntu2 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 11.1.1-1ubuntu2 version.xserver-xorg-core: xserver-xorg-core 2:1.17.3-2ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.2-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.6.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20160127-1ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1 xserver.bootTime: Mon Feb 8 17:08:14 2016 xserver.configfile: default xserver.errors: systemd-logind: failed to get session: PID 9847 does not belong to any know
[Desktop-packages] [Bug 1771749] CRDA.txt
apport information ** Attachment added: "CRDA.txt" https://bugs.launchpad.net/bugs/1771749/+attachment/5140824/+files/CRDA.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1771749 Title: Ethernet connection lost after few minutes since starting Status in linux package in Ubuntu: Confirmed Status in network-manager package in Ubuntu: New Bug description: This is the same bug I notified at Bug #1770848 but with a more precise selection of (what I think it is) the package affected and a better description. I made a few days ago a fresh install of the Kubuntu 18.04 LTS and it is most everything Ok, but -I think that- the network-manager has a problem. In the last LTS version, Kubuntu 16.04, nor in any Linux version if I remember well, I never lost connection through Ethernet (the only Internet connection with our desktop PC), but the Bionic Beaver loses the connection every now and then, perhaps within few minutes or hours, but several times per day. When the connection is lost, I note that it disappears any info even mention to any network into the network window and the network manager icon becomes red color. Not matter if I unplug and then plug the ethernet cable again, the ethernet connection is not longer detected and only restarting the PC makes the connection to work again. Incidentally, I also have noticed with this version of Kubuntu 18.04 that in my laptop there is also now a similar problem with the scanner: If I plug it in some USB port of the laptop once Kubuntu 18.04 is already running, it's not detected by Xsane. I have to plug it in before than pressing the power button or at the time of starting the OS, for the scanner to be detected by the scanning program (and then only works with Xsane, not if I use Simple Scan or Skanlite, even when it works under Xsane), as I said in the Bug #1771525 and, evenly, if I unplug the scanner cable from the USB port it is not detected anymore when plugging it again, and only restarting the laptop makes it to be detected. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: network-manager 1.10.6-2ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 CurrentDesktop: KDE Date: Thu May 17 08:24:23 2018 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2018-05-11 (5 days ago) InstallationMedia: Kubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) IpRoute: default via 192.168.1.1 dev enp0s7 proto static metric 100 169.254.0.0/16 dev enp0s7 scope link metric 1000 192.168.1.0/24 dev enp0s7 proto kernel scope link src 192.168.1.3 metric 100 IwConfig: enp0s7no wireless extensions. lono wireless extensions. NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true PciNetwork: RfKill: SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) nmcli-con: NAME UUID TYPE TIMESTAMP TIMESTAMP-REAL AUTOCONNECT AUTOCONNECT-PRIORITY READONLY DBUS-PATH ACTIVE DEVICE STATE ACTIVE-PATH SLAVE Conexión cableada 1 1cc37db8-0db8-3887-acf2-59fbbcd0cb1c ethernet 1526538083 jue 17 may 2018 08:21:23 CEST yes 4294967196 no/org/freedesktop/NetworkManager/Settings/1 yes enp0s7 activated /org/freedesktop/NetworkManager/ActiveConnection/1 -- nmcli-dev: DEVICE TYPE STATE DBUS-PATH CONNECTION CON-UUID CON-PATH enp0s7 ethernet connected /org/freedesktop/NetworkManager/Devices/2 Conexión cableada 1 1cc37db8-0db8-3887-acf2-59fbbcd0cb1c /org/freedesktop/NetworkManager/ActiveConnection/1 lo loopback unmanaged /org/freedesktop/NetworkManager/Devices/1 -- ---- nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.10.6 connected started full enabled enabled enabled enabled enabled --- ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: nosotros 1116 F pulseaudio /dev/snd/controlC1: nosotros 1116 F pulseaudio CurrentDesktop: KDE DistroRelease: Ubuntu 18.04 HibernationDevice: RESUME=UUID=bb1531db-e7c0-48eb-a5b7-5afe3df47ba3 IfupdownConfig: # i
[Desktop-packages] [Bug 1771749] NetDevice.enp0s7.txt
apport information ** Attachment added: "NetDevice.enp0s7.txt" https://bugs.launchpad.net/bugs/1771749/+attachment/5140829/+files/NetDevice.enp0s7.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1771749 Title: Ethernet connection lost after few minutes since starting Status in linux package in Ubuntu: Confirmed Status in network-manager package in Ubuntu: New Bug description: This is the same bug I notified at Bug #1770848 but with a more precise selection of (what I think it is) the package affected and a better description. I made a few days ago a fresh install of the Kubuntu 18.04 LTS and it is most everything Ok, but -I think that- the network-manager has a problem. In the last LTS version, Kubuntu 16.04, nor in any Linux version if I remember well, I never lost connection through Ethernet (the only Internet connection with our desktop PC), but the Bionic Beaver loses the connection every now and then, perhaps within few minutes or hours, but several times per day. When the connection is lost, I note that it disappears any info even mention to any network into the network window and the network manager icon becomes red color. Not matter if I unplug and then plug the ethernet cable again, the ethernet connection is not longer detected and only restarting the PC makes the connection to work again. Incidentally, I also have noticed with this version of Kubuntu 18.04 that in my laptop there is also now a similar problem with the scanner: If I plug it in some USB port of the laptop once Kubuntu 18.04 is already running, it's not detected by Xsane. I have to plug it in before than pressing the power button or at the time of starting the OS, for the scanner to be detected by the scanning program (and then only works with Xsane, not if I use Simple Scan or Skanlite, even when it works under Xsane), as I said in the Bug #1771525 and, evenly, if I unplug the scanner cable from the USB port it is not detected anymore when plugging it again, and only restarting the laptop makes it to be detected. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: network-manager 1.10.6-2ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 CurrentDesktop: KDE Date: Thu May 17 08:24:23 2018 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2018-05-11 (5 days ago) InstallationMedia: Kubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) IpRoute: default via 192.168.1.1 dev enp0s7 proto static metric 100 169.254.0.0/16 dev enp0s7 scope link metric 1000 192.168.1.0/24 dev enp0s7 proto kernel scope link src 192.168.1.3 metric 100 IwConfig: enp0s7no wireless extensions. lono wireless extensions. NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true PciNetwork: RfKill: SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) nmcli-con: NAME UUID TYPE TIMESTAMP TIMESTAMP-REAL AUTOCONNECT AUTOCONNECT-PRIORITY READONLY DBUS-PATH ACTIVE DEVICE STATE ACTIVE-PATH SLAVE Conexión cableada 1 1cc37db8-0db8-3887-acf2-59fbbcd0cb1c ethernet 1526538083 jue 17 may 2018 08:21:23 CEST yes 4294967196 no/org/freedesktop/NetworkManager/Settings/1 yes enp0s7 activated /org/freedesktop/NetworkManager/ActiveConnection/1 -- nmcli-dev: DEVICE TYPE STATE DBUS-PATH CONNECTION CON-UUID CON-PATH enp0s7 ethernet connected /org/freedesktop/NetworkManager/Devices/2 Conexión cableada 1 1cc37db8-0db8-3887-acf2-59fbbcd0cb1c /org/freedesktop/NetworkManager/ActiveConnection/1 lo loopback unmanaged /org/freedesktop/NetworkManager/Devices/1 -- ---- nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.10.6 connected started full enabled enabled enabled enabled enabled --- ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: nosotros 1116 F pulseaudio /dev/snd/controlC1: nosotros 1116 F pulseaudio CurrentDesktop: KDE DistroRelease: Ubuntu 18.04 HibernationDevice: RESUME=UUID=bb1531db-e7c0-48eb-a5b7-5afe3df47ba3
[Desktop-packages] [Bug 1771749] Re: Ethernet connection lost after few minutes since starting
apport information ** Tags added: apport-collected ** Description changed: This is the same bug I notified at Bug #1770848 but with a more precise selection of (what I think it is) the package affected and a better description. I made a few days ago a fresh install of the Kubuntu 18.04 LTS and it is most everything Ok, but -I think that- the network-manager has a problem. In the last LTS version, Kubuntu 16.04, nor in any Linux version if I remember well, I never lost connection through Ethernet (the only Internet connection with our desktop PC), but the Bionic Beaver loses the connection every now and then, perhaps within few minutes or hours, but several times per day. When the connection is lost, I note that it disappears any info even mention to any network into the network window and the network manager icon becomes red color. Not matter if I unplug and then plug the ethernet cable again, the ethernet connection is not longer detected and only restarting the PC makes the connection to work again. Incidentally, I also have noticed with this version of Kubuntu 18.04 that in my laptop there is also now a similar problem with the scanner: If I plug it in some USB port of the laptop once Kubuntu 18.04 is already running, it's not detected by Xsane. I have to plug it in before than pressing the power button or at the time of starting the OS, for the scanner to be detected by the scanning program (and then only works with Xsane, not if I use Simple Scan or Skanlite, even when it works under Xsane), as I said in the Bug #1771525 and, evenly, if I unplug the scanner cable from the USB port it is not detected anymore when plugging it again, and only restarting the laptop makes it to be detected. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: network-manager 1.10.6-2ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 CurrentDesktop: KDE Date: Thu May 17 08:24:23 2018 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2018-05-11 (5 days ago) InstallationMedia: Kubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) IpRoute: default via 192.168.1.1 dev enp0s7 proto static metric 100 169.254.0.0/16 dev enp0s7 scope link metric 1000 192.168.1.0/24 dev enp0s7 proto kernel scope link src 192.168.1.3 metric 100 IwConfig: enp0s7no wireless extensions. lono wireless extensions. NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true PciNetwork: RfKill: SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) nmcli-con: NAME UUID TYPE TIMESTAMP TIMESTAMP-REAL AUTOCONNECT AUTOCONNECT-PRIORITY READONLY DBUS-PATH ACTIVE DEVICE STATE ACTIVE-PATH SLAVE Conexión cableada 1 1cc37db8-0db8-3887-acf2-59fbbcd0cb1c ethernet 1526538083 jue 17 may 2018 08:21:23 CEST yes 4294967196 no/org/freedesktop/NetworkManager/Settings/1 yes enp0s7 activated /org/freedesktop/NetworkManager/ActiveConnection/1 -- nmcli-dev: DEVICE TYPE STATE DBUS-PATH CONNECTION CON-UUID CON-PATH enp0s7 ethernet connected /org/freedesktop/NetworkManager/Devices/2 Conexión cableada 1 1cc37db8-0db8-3887-acf2-59fbbcd0cb1c /org/freedesktop/NetworkManager/ActiveConnection/1 lo loopback unmanaged /org/freedesktop/NetworkManager/Devices/1 -- ---- nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.10.6 connected started full enabled enabled enabled enabled enabled + --- + ApportVersion: 2.20.9-0ubuntu7 + Architecture: amd64 + AudioDevicesInUse: + USERPID ACCESS COMMAND + /dev/snd/controlC0: nosotros 1116 F pulseaudio + /dev/snd/controlC1: nosotros 1116 F pulseaudio + CurrentDesktop: KDE + DistroRelease: Ubuntu 18.04 + HibernationDevice: RESUME=UUID=bb1531db-e7c0-48eb-a5b7-5afe3df47ba3 + IfupdownConfig: + # interfaces(5) file used by ifup(8) and ifdown(8) + auto lo + iface lo inet loopback + InstallationDate: Installed on 2018-05-11 (6 days ago) + InstallationMedia: Kubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) + IpRoute: + default via 192.168.1.1 dev enp0s7 proto static metric 100 + 169.254.0.0/16 dev enp0s7 scope link metric 1000 + 192.168.1.0/24 dev enp0s7 proto kernel scope link
[Desktop-packages] [Bug 1771749] CurrentDmesg.txt
apport information ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/1771749/+attachment/5140825/+files/CurrentDmesg.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1771749 Title: Ethernet connection lost after few minutes since starting Status in linux package in Ubuntu: Confirmed Status in network-manager package in Ubuntu: New Bug description: This is the same bug I notified at Bug #1770848 but with a more precise selection of (what I think it is) the package affected and a better description. I made a few days ago a fresh install of the Kubuntu 18.04 LTS and it is most everything Ok, but -I think that- the network-manager has a problem. In the last LTS version, Kubuntu 16.04, nor in any Linux version if I remember well, I never lost connection through Ethernet (the only Internet connection with our desktop PC), but the Bionic Beaver loses the connection every now and then, perhaps within few minutes or hours, but several times per day. When the connection is lost, I note that it disappears any info even mention to any network into the network window and the network manager icon becomes red color. Not matter if I unplug and then plug the ethernet cable again, the ethernet connection is not longer detected and only restarting the PC makes the connection to work again. Incidentally, I also have noticed with this version of Kubuntu 18.04 that in my laptop there is also now a similar problem with the scanner: If I plug it in some USB port of the laptop once Kubuntu 18.04 is already running, it's not detected by Xsane. I have to plug it in before than pressing the power button or at the time of starting the OS, for the scanner to be detected by the scanning program (and then only works with Xsane, not if I use Simple Scan or Skanlite, even when it works under Xsane), as I said in the Bug #1771525 and, evenly, if I unplug the scanner cable from the USB port it is not detected anymore when plugging it again, and only restarting the laptop makes it to be detected. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: network-manager 1.10.6-2ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 CurrentDesktop: KDE Date: Thu May 17 08:24:23 2018 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2018-05-11 (5 days ago) InstallationMedia: Kubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) IpRoute: default via 192.168.1.1 dev enp0s7 proto static metric 100 169.254.0.0/16 dev enp0s7 scope link metric 1000 192.168.1.0/24 dev enp0s7 proto kernel scope link src 192.168.1.3 metric 100 IwConfig: enp0s7no wireless extensions. lono wireless extensions. NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true PciNetwork: RfKill: SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) nmcli-con: NAME UUID TYPE TIMESTAMP TIMESTAMP-REAL AUTOCONNECT AUTOCONNECT-PRIORITY READONLY DBUS-PATH ACTIVE DEVICE STATE ACTIVE-PATH SLAVE Conexión cableada 1 1cc37db8-0db8-3887-acf2-59fbbcd0cb1c ethernet 1526538083 jue 17 may 2018 08:21:23 CEST yes 4294967196 no/org/freedesktop/NetworkManager/Settings/1 yes enp0s7 activated /org/freedesktop/NetworkManager/ActiveConnection/1 -- nmcli-dev: DEVICE TYPE STATE DBUS-PATH CONNECTION CON-UUID CON-PATH enp0s7 ethernet connected /org/freedesktop/NetworkManager/Devices/2 Conexión cableada 1 1cc37db8-0db8-3887-acf2-59fbbcd0cb1c /org/freedesktop/NetworkManager/ActiveConnection/1 lo loopback unmanaged /org/freedesktop/NetworkManager/Devices/1 -- ---- nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.10.6 connected started full enabled enabled enabled enabled enabled --- ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: nosotros 1116 F pulseaudio /dev/snd/controlC1: nosotros 1116 F pulseaudio CurrentDesktop: KDE DistroRelease: Ubuntu 18.04 HibernationDevice: RESUME=UUID=bb1531db-e7c0-48eb-a5b7-5afe3df47ba3 Ifupd
[Desktop-packages] [Bug 1771749] NetDevice.lo.txt
apport information ** Attachment added: "NetDevice.lo.txt" https://bugs.launchpad.net/bugs/1771749/+attachment/5140830/+files/NetDevice.lo.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1771749 Title: Ethernet connection lost after few minutes since starting Status in linux package in Ubuntu: Confirmed Status in network-manager package in Ubuntu: New Bug description: This is the same bug I notified at Bug #1770848 but with a more precise selection of (what I think it is) the package affected and a better description. I made a few days ago a fresh install of the Kubuntu 18.04 LTS and it is most everything Ok, but -I think that- the network-manager has a problem. In the last LTS version, Kubuntu 16.04, nor in any Linux version if I remember well, I never lost connection through Ethernet (the only Internet connection with our desktop PC), but the Bionic Beaver loses the connection every now and then, perhaps within few minutes or hours, but several times per day. When the connection is lost, I note that it disappears any info even mention to any network into the network window and the network manager icon becomes red color. Not matter if I unplug and then plug the ethernet cable again, the ethernet connection is not longer detected and only restarting the PC makes the connection to work again. Incidentally, I also have noticed with this version of Kubuntu 18.04 that in my laptop there is also now a similar problem with the scanner: If I plug it in some USB port of the laptop once Kubuntu 18.04 is already running, it's not detected by Xsane. I have to plug it in before than pressing the power button or at the time of starting the OS, for the scanner to be detected by the scanning program (and then only works with Xsane, not if I use Simple Scan or Skanlite, even when it works under Xsane), as I said in the Bug #1771525 and, evenly, if I unplug the scanner cable from the USB port it is not detected anymore when plugging it again, and only restarting the laptop makes it to be detected. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: network-manager 1.10.6-2ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 CurrentDesktop: KDE Date: Thu May 17 08:24:23 2018 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2018-05-11 (5 days ago) InstallationMedia: Kubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) IpRoute: default via 192.168.1.1 dev enp0s7 proto static metric 100 169.254.0.0/16 dev enp0s7 scope link metric 1000 192.168.1.0/24 dev enp0s7 proto kernel scope link src 192.168.1.3 metric 100 IwConfig: enp0s7no wireless extensions. lono wireless extensions. NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true PciNetwork: RfKill: SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) nmcli-con: NAME UUID TYPE TIMESTAMP TIMESTAMP-REAL AUTOCONNECT AUTOCONNECT-PRIORITY READONLY DBUS-PATH ACTIVE DEVICE STATE ACTIVE-PATH SLAVE Conexión cableada 1 1cc37db8-0db8-3887-acf2-59fbbcd0cb1c ethernet 1526538083 jue 17 may 2018 08:21:23 CEST yes 4294967196 no/org/freedesktop/NetworkManager/Settings/1 yes enp0s7 activated /org/freedesktop/NetworkManager/ActiveConnection/1 -- nmcli-dev: DEVICE TYPE STATE DBUS-PATH CONNECTION CON-UUID CON-PATH enp0s7 ethernet connected /org/freedesktop/NetworkManager/Devices/2 Conexión cableada 1 1cc37db8-0db8-3887-acf2-59fbbcd0cb1c /org/freedesktop/NetworkManager/ActiveConnection/1 lo loopback unmanaged /org/freedesktop/NetworkManager/Devices/1 -- ---- nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.10.6 connected started full enabled enabled enabled enabled enabled --- ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: nosotros 1116 F pulseaudio /dev/snd/controlC1: nosotros 1116 F pulseaudio CurrentDesktop: KDE DistroRelease: Ubuntu 18.04 HibernationDevice: RESUME=UUID=bb1531db-e7c0-48eb-a5b7-5afe3df47ba3 Ifupd
[Desktop-packages] [Bug 1771749] Dependencies.txt
apport information ** Attachment added: "Dependencies.txt" https://bugs.launchpad.net/bugs/1771749/+attachment/5140826/+files/Dependencies.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1771749 Title: Ethernet connection lost after few minutes since starting Status in linux package in Ubuntu: Confirmed Status in network-manager package in Ubuntu: New Bug description: This is the same bug I notified at Bug #1770848 but with a more precise selection of (what I think it is) the package affected and a better description. I made a few days ago a fresh install of the Kubuntu 18.04 LTS and it is most everything Ok, but -I think that- the network-manager has a problem. In the last LTS version, Kubuntu 16.04, nor in any Linux version if I remember well, I never lost connection through Ethernet (the only Internet connection with our desktop PC), but the Bionic Beaver loses the connection every now and then, perhaps within few minutes or hours, but several times per day. When the connection is lost, I note that it disappears any info even mention to any network into the network window and the network manager icon becomes red color. Not matter if I unplug and then plug the ethernet cable again, the ethernet connection is not longer detected and only restarting the PC makes the connection to work again. Incidentally, I also have noticed with this version of Kubuntu 18.04 that in my laptop there is also now a similar problem with the scanner: If I plug it in some USB port of the laptop once Kubuntu 18.04 is already running, it's not detected by Xsane. I have to plug it in before than pressing the power button or at the time of starting the OS, for the scanner to be detected by the scanning program (and then only works with Xsane, not if I use Simple Scan or Skanlite, even when it works under Xsane), as I said in the Bug #1771525 and, evenly, if I unplug the scanner cable from the USB port it is not detected anymore when plugging it again, and only restarting the laptop makes it to be detected. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: network-manager 1.10.6-2ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 CurrentDesktop: KDE Date: Thu May 17 08:24:23 2018 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2018-05-11 (5 days ago) InstallationMedia: Kubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) IpRoute: default via 192.168.1.1 dev enp0s7 proto static metric 100 169.254.0.0/16 dev enp0s7 scope link metric 1000 192.168.1.0/24 dev enp0s7 proto kernel scope link src 192.168.1.3 metric 100 IwConfig: enp0s7no wireless extensions. lono wireless extensions. NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true PciNetwork: RfKill: SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) nmcli-con: NAME UUID TYPE TIMESTAMP TIMESTAMP-REAL AUTOCONNECT AUTOCONNECT-PRIORITY READONLY DBUS-PATH ACTIVE DEVICE STATE ACTIVE-PATH SLAVE Conexión cableada 1 1cc37db8-0db8-3887-acf2-59fbbcd0cb1c ethernet 1526538083 jue 17 may 2018 08:21:23 CEST yes 4294967196 no/org/freedesktop/NetworkManager/Settings/1 yes enp0s7 activated /org/freedesktop/NetworkManager/ActiveConnection/1 -- nmcli-dev: DEVICE TYPE STATE DBUS-PATH CONNECTION CON-UUID CON-PATH enp0s7 ethernet connected /org/freedesktop/NetworkManager/Devices/2 Conexión cableada 1 1cc37db8-0db8-3887-acf2-59fbbcd0cb1c /org/freedesktop/NetworkManager/ActiveConnection/1 lo loopback unmanaged /org/freedesktop/NetworkManager/Devices/1 -- ---- nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.10.6 connected started full enabled enabled enabled enabled enabled --- ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: nosotros 1116 F pulseaudio /dev/snd/controlC1: nosotros 1116 F pulseaudio CurrentDesktop: KDE DistroRelease: Ubuntu 18.04 HibernationDevice: RESUME=UUID=bb1531db-e7c0-48eb-a5b7-5afe3df47ba3 Ifupd
[Desktop-packages] [Bug 1771749] Lspci.txt
apport information ** Attachment added: "Lspci.txt" https://bugs.launchpad.net/bugs/1771749/+attachment/5140828/+files/Lspci.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1771749 Title: Ethernet connection lost after few minutes since starting Status in linux package in Ubuntu: Confirmed Status in network-manager package in Ubuntu: New Bug description: This is the same bug I notified at Bug #1770848 but with a more precise selection of (what I think it is) the package affected and a better description. I made a few days ago a fresh install of the Kubuntu 18.04 LTS and it is most everything Ok, but -I think that- the network-manager has a problem. In the last LTS version, Kubuntu 16.04, nor in any Linux version if I remember well, I never lost connection through Ethernet (the only Internet connection with our desktop PC), but the Bionic Beaver loses the connection every now and then, perhaps within few minutes or hours, but several times per day. When the connection is lost, I note that it disappears any info even mention to any network into the network window and the network manager icon becomes red color. Not matter if I unplug and then plug the ethernet cable again, the ethernet connection is not longer detected and only restarting the PC makes the connection to work again. Incidentally, I also have noticed with this version of Kubuntu 18.04 that in my laptop there is also now a similar problem with the scanner: If I plug it in some USB port of the laptop once Kubuntu 18.04 is already running, it's not detected by Xsane. I have to plug it in before than pressing the power button or at the time of starting the OS, for the scanner to be detected by the scanning program (and then only works with Xsane, not if I use Simple Scan or Skanlite, even when it works under Xsane), as I said in the Bug #1771525 and, evenly, if I unplug the scanner cable from the USB port it is not detected anymore when plugging it again, and only restarting the laptop makes it to be detected. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: network-manager 1.10.6-2ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 CurrentDesktop: KDE Date: Thu May 17 08:24:23 2018 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2018-05-11 (5 days ago) InstallationMedia: Kubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) IpRoute: default via 192.168.1.1 dev enp0s7 proto static metric 100 169.254.0.0/16 dev enp0s7 scope link metric 1000 192.168.1.0/24 dev enp0s7 proto kernel scope link src 192.168.1.3 metric 100 IwConfig: enp0s7no wireless extensions. lono wireless extensions. NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true PciNetwork: RfKill: SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) nmcli-con: NAME UUID TYPE TIMESTAMP TIMESTAMP-REAL AUTOCONNECT AUTOCONNECT-PRIORITY READONLY DBUS-PATH ACTIVE DEVICE STATE ACTIVE-PATH SLAVE Conexión cableada 1 1cc37db8-0db8-3887-acf2-59fbbcd0cb1c ethernet 1526538083 jue 17 may 2018 08:21:23 CEST yes 4294967196 no/org/freedesktop/NetworkManager/Settings/1 yes enp0s7 activated /org/freedesktop/NetworkManager/ActiveConnection/1 -- nmcli-dev: DEVICE TYPE STATE DBUS-PATH CONNECTION CON-UUID CON-PATH enp0s7 ethernet connected /org/freedesktop/NetworkManager/Devices/2 Conexión cableada 1 1cc37db8-0db8-3887-acf2-59fbbcd0cb1c /org/freedesktop/NetworkManager/ActiveConnection/1 lo loopback unmanaged /org/freedesktop/NetworkManager/Devices/1 -- ---- nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.10.6 connected started full enabled enabled enabled enabled enabled --- ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: nosotros 1116 F pulseaudio /dev/snd/controlC1: nosotros 1116 F pulseaudio CurrentDesktop: KDE DistroRelease: Ubuntu 18.04 HibernationDevice: RESUME=UUID=bb1531db-e7c0-48eb-a5b7-5afe3df47ba3 IfupdownConfig: #
[Desktop-packages] [Bug 1771749] IpAddr.txt
apport information ** Attachment added: "IpAddr.txt" https://bugs.launchpad.net/bugs/1771749/+attachment/5140827/+files/IpAddr.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1771749 Title: Ethernet connection lost after few minutes since starting Status in linux package in Ubuntu: Confirmed Status in network-manager package in Ubuntu: New Bug description: This is the same bug I notified at Bug #1770848 but with a more precise selection of (what I think it is) the package affected and a better description. I made a few days ago a fresh install of the Kubuntu 18.04 LTS and it is most everything Ok, but -I think that- the network-manager has a problem. In the last LTS version, Kubuntu 16.04, nor in any Linux version if I remember well, I never lost connection through Ethernet (the only Internet connection with our desktop PC), but the Bionic Beaver loses the connection every now and then, perhaps within few minutes or hours, but several times per day. When the connection is lost, I note that it disappears any info even mention to any network into the network window and the network manager icon becomes red color. Not matter if I unplug and then plug the ethernet cable again, the ethernet connection is not longer detected and only restarting the PC makes the connection to work again. Incidentally, I also have noticed with this version of Kubuntu 18.04 that in my laptop there is also now a similar problem with the scanner: If I plug it in some USB port of the laptop once Kubuntu 18.04 is already running, it's not detected by Xsane. I have to plug it in before than pressing the power button or at the time of starting the OS, for the scanner to be detected by the scanning program (and then only works with Xsane, not if I use Simple Scan or Skanlite, even when it works under Xsane), as I said in the Bug #1771525 and, evenly, if I unplug the scanner cable from the USB port it is not detected anymore when plugging it again, and only restarting the laptop makes it to be detected. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: network-manager 1.10.6-2ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 CurrentDesktop: KDE Date: Thu May 17 08:24:23 2018 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2018-05-11 (5 days ago) InstallationMedia: Kubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) IpRoute: default via 192.168.1.1 dev enp0s7 proto static metric 100 169.254.0.0/16 dev enp0s7 scope link metric 1000 192.168.1.0/24 dev enp0s7 proto kernel scope link src 192.168.1.3 metric 100 IwConfig: enp0s7no wireless extensions. lono wireless extensions. NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true PciNetwork: RfKill: SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) nmcli-con: NAME UUID TYPE TIMESTAMP TIMESTAMP-REAL AUTOCONNECT AUTOCONNECT-PRIORITY READONLY DBUS-PATH ACTIVE DEVICE STATE ACTIVE-PATH SLAVE Conexión cableada 1 1cc37db8-0db8-3887-acf2-59fbbcd0cb1c ethernet 1526538083 jue 17 may 2018 08:21:23 CEST yes 4294967196 no/org/freedesktop/NetworkManager/Settings/1 yes enp0s7 activated /org/freedesktop/NetworkManager/ActiveConnection/1 -- nmcli-dev: DEVICE TYPE STATE DBUS-PATH CONNECTION CON-UUID CON-PATH enp0s7 ethernet connected /org/freedesktop/NetworkManager/Devices/2 Conexión cableada 1 1cc37db8-0db8-3887-acf2-59fbbcd0cb1c /org/freedesktop/NetworkManager/ActiveConnection/1 lo loopback unmanaged /org/freedesktop/NetworkManager/Devices/1 -- ---- nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.10.6 connected started full enabled enabled enabled enabled enabled --- ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: nosotros 1116 F pulseaudio /dev/snd/controlC1: nosotros 1116 F pulseaudio CurrentDesktop: KDE DistroRelease: Ubuntu 18.04 HibernationDevice: RESUME=UUID=bb1531db-e7c0-48eb-a5b7-5afe3df47ba3 IfupdownConfig:
[Desktop-packages] [Bug 1771749] ProcEnviron.txt
apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/1771749/+attachment/5140833/+files/ProcEnviron.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1771749 Title: Ethernet connection lost after few minutes since starting Status in linux package in Ubuntu: Confirmed Status in network-manager package in Ubuntu: New Bug description: This is the same bug I notified at Bug #1770848 but with a more precise selection of (what I think it is) the package affected and a better description. I made a few days ago a fresh install of the Kubuntu 18.04 LTS and it is most everything Ok, but -I think that- the network-manager has a problem. In the last LTS version, Kubuntu 16.04, nor in any Linux version if I remember well, I never lost connection through Ethernet (the only Internet connection with our desktop PC), but the Bionic Beaver loses the connection every now and then, perhaps within few minutes or hours, but several times per day. When the connection is lost, I note that it disappears any info even mention to any network into the network window and the network manager icon becomes red color. Not matter if I unplug and then plug the ethernet cable again, the ethernet connection is not longer detected and only restarting the PC makes the connection to work again. Incidentally, I also have noticed with this version of Kubuntu 18.04 that in my laptop there is also now a similar problem with the scanner: If I plug it in some USB port of the laptop once Kubuntu 18.04 is already running, it's not detected by Xsane. I have to plug it in before than pressing the power button or at the time of starting the OS, for the scanner to be detected by the scanning program (and then only works with Xsane, not if I use Simple Scan or Skanlite, even when it works under Xsane), as I said in the Bug #1771525 and, evenly, if I unplug the scanner cable from the USB port it is not detected anymore when plugging it again, and only restarting the laptop makes it to be detected. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: network-manager 1.10.6-2ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 CurrentDesktop: KDE Date: Thu May 17 08:24:23 2018 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2018-05-11 (5 days ago) InstallationMedia: Kubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) IpRoute: default via 192.168.1.1 dev enp0s7 proto static metric 100 169.254.0.0/16 dev enp0s7 scope link metric 1000 192.168.1.0/24 dev enp0s7 proto kernel scope link src 192.168.1.3 metric 100 IwConfig: enp0s7no wireless extensions. lono wireless extensions. NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true PciNetwork: RfKill: SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) nmcli-con: NAME UUID TYPE TIMESTAMP TIMESTAMP-REAL AUTOCONNECT AUTOCONNECT-PRIORITY READONLY DBUS-PATH ACTIVE DEVICE STATE ACTIVE-PATH SLAVE Conexión cableada 1 1cc37db8-0db8-3887-acf2-59fbbcd0cb1c ethernet 1526538083 jue 17 may 2018 08:21:23 CEST yes 4294967196 no/org/freedesktop/NetworkManager/Settings/1 yes enp0s7 activated /org/freedesktop/NetworkManager/ActiveConnection/1 -- nmcli-dev: DEVICE TYPE STATE DBUS-PATH CONNECTION CON-UUID CON-PATH enp0s7 ethernet connected /org/freedesktop/NetworkManager/Devices/2 Conexión cableada 1 1cc37db8-0db8-3887-acf2-59fbbcd0cb1c /org/freedesktop/NetworkManager/ActiveConnection/1 lo loopback unmanaged /org/freedesktop/NetworkManager/Devices/1 -- ---- nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.10.6 connected started full enabled enabled enabled enabled enabled --- ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: nosotros 1116 F pulseaudio /dev/snd/controlC1: nosotros 1116 F pulseaudio CurrentDesktop: KDE DistroRelease: Ubuntu 18.04 HibernationDevice: RESUME=UUID=bb1531db-e7c0-48eb-a5b7-5afe3df47ba3 Ifupdow
[Desktop-packages] [Bug 1771749] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/1771749/+attachment/5140834/+files/ProcInterrupts.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1771749 Title: Ethernet connection lost after few minutes since starting Status in linux package in Ubuntu: Confirmed Status in network-manager package in Ubuntu: New Bug description: This is the same bug I notified at Bug #1770848 but with a more precise selection of (what I think it is) the package affected and a better description. I made a few days ago a fresh install of the Kubuntu 18.04 LTS and it is most everything Ok, but -I think that- the network-manager has a problem. In the last LTS version, Kubuntu 16.04, nor in any Linux version if I remember well, I never lost connection through Ethernet (the only Internet connection with our desktop PC), but the Bionic Beaver loses the connection every now and then, perhaps within few minutes or hours, but several times per day. When the connection is lost, I note that it disappears any info even mention to any network into the network window and the network manager icon becomes red color. Not matter if I unplug and then plug the ethernet cable again, the ethernet connection is not longer detected and only restarting the PC makes the connection to work again. Incidentally, I also have noticed with this version of Kubuntu 18.04 that in my laptop there is also now a similar problem with the scanner: If I plug it in some USB port of the laptop once Kubuntu 18.04 is already running, it's not detected by Xsane. I have to plug it in before than pressing the power button or at the time of starting the OS, for the scanner to be detected by the scanning program (and then only works with Xsane, not if I use Simple Scan or Skanlite, even when it works under Xsane), as I said in the Bug #1771525 and, evenly, if I unplug the scanner cable from the USB port it is not detected anymore when plugging it again, and only restarting the laptop makes it to be detected. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: network-manager 1.10.6-2ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 CurrentDesktop: KDE Date: Thu May 17 08:24:23 2018 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2018-05-11 (5 days ago) InstallationMedia: Kubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) IpRoute: default via 192.168.1.1 dev enp0s7 proto static metric 100 169.254.0.0/16 dev enp0s7 scope link metric 1000 192.168.1.0/24 dev enp0s7 proto kernel scope link src 192.168.1.3 metric 100 IwConfig: enp0s7no wireless extensions. lono wireless extensions. NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true PciNetwork: RfKill: SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) nmcli-con: NAME UUID TYPE TIMESTAMP TIMESTAMP-REAL AUTOCONNECT AUTOCONNECT-PRIORITY READONLY DBUS-PATH ACTIVE DEVICE STATE ACTIVE-PATH SLAVE Conexión cableada 1 1cc37db8-0db8-3887-acf2-59fbbcd0cb1c ethernet 1526538083 jue 17 may 2018 08:21:23 CEST yes 4294967196 no/org/freedesktop/NetworkManager/Settings/1 yes enp0s7 activated /org/freedesktop/NetworkManager/ActiveConnection/1 -- nmcli-dev: DEVICE TYPE STATE DBUS-PATH CONNECTION CON-UUID CON-PATH enp0s7 ethernet connected /org/freedesktop/NetworkManager/Devices/2 Conexión cableada 1 1cc37db8-0db8-3887-acf2-59fbbcd0cb1c /org/freedesktop/NetworkManager/ActiveConnection/1 lo loopback unmanaged /org/freedesktop/NetworkManager/Devices/1 -- ---- nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.10.6 connected started full enabled enabled enabled enabled enabled --- ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: nosotros 1116 F pulseaudio /dev/snd/controlC1: nosotros 1116 F pulseaudio CurrentDesktop: KDE DistroRelease: Ubuntu 18.04 HibernationDevice: RESUME=UUID=bb1531db-e7c0-48eb-a5b7-5afe3df47ba3 I
[Desktop-packages] [Bug 1771749] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1771749/+attachment/5140832/+files/ProcCpuinfoMinimal.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1771749 Title: Ethernet connection lost after few minutes since starting Status in linux package in Ubuntu: Confirmed Status in network-manager package in Ubuntu: New Bug description: This is the same bug I notified at Bug #1770848 but with a more precise selection of (what I think it is) the package affected and a better description. I made a few days ago a fresh install of the Kubuntu 18.04 LTS and it is most everything Ok, but -I think that- the network-manager has a problem. In the last LTS version, Kubuntu 16.04, nor in any Linux version if I remember well, I never lost connection through Ethernet (the only Internet connection with our desktop PC), but the Bionic Beaver loses the connection every now and then, perhaps within few minutes or hours, but several times per day. When the connection is lost, I note that it disappears any info even mention to any network into the network window and the network manager icon becomes red color. Not matter if I unplug and then plug the ethernet cable again, the ethernet connection is not longer detected and only restarting the PC makes the connection to work again. Incidentally, I also have noticed with this version of Kubuntu 18.04 that in my laptop there is also now a similar problem with the scanner: If I plug it in some USB port of the laptop once Kubuntu 18.04 is already running, it's not detected by Xsane. I have to plug it in before than pressing the power button or at the time of starting the OS, for the scanner to be detected by the scanning program (and then only works with Xsane, not if I use Simple Scan or Skanlite, even when it works under Xsane), as I said in the Bug #1771525 and, evenly, if I unplug the scanner cable from the USB port it is not detected anymore when plugging it again, and only restarting the laptop makes it to be detected. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: network-manager 1.10.6-2ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 CurrentDesktop: KDE Date: Thu May 17 08:24:23 2018 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2018-05-11 (5 days ago) InstallationMedia: Kubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) IpRoute: default via 192.168.1.1 dev enp0s7 proto static metric 100 169.254.0.0/16 dev enp0s7 scope link metric 1000 192.168.1.0/24 dev enp0s7 proto kernel scope link src 192.168.1.3 metric 100 IwConfig: enp0s7no wireless extensions. lono wireless extensions. NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true PciNetwork: RfKill: SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) nmcli-con: NAME UUID TYPE TIMESTAMP TIMESTAMP-REAL AUTOCONNECT AUTOCONNECT-PRIORITY READONLY DBUS-PATH ACTIVE DEVICE STATE ACTIVE-PATH SLAVE Conexión cableada 1 1cc37db8-0db8-3887-acf2-59fbbcd0cb1c ethernet 1526538083 jue 17 may 2018 08:21:23 CEST yes 4294967196 no/org/freedesktop/NetworkManager/Settings/1 yes enp0s7 activated /org/freedesktop/NetworkManager/ActiveConnection/1 -- nmcli-dev: DEVICE TYPE STATE DBUS-PATH CONNECTION CON-UUID CON-PATH enp0s7 ethernet connected /org/freedesktop/NetworkManager/Devices/2 Conexión cableada 1 1cc37db8-0db8-3887-acf2-59fbbcd0cb1c /org/freedesktop/NetworkManager/ActiveConnection/1 lo loopback unmanaged /org/freedesktop/NetworkManager/Devices/1 -- ---- nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.10.6 connected started full enabled enabled enabled enabled enabled --- ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: nosotros 1116 F pulseaudio /dev/snd/controlC1: nosotros 1116 F pulseaudio CurrentDesktop: KDE DistroRelease: Ubuntu 18.04 HibernationDevice: RESUME=UUID=bb1531db-e7c0-48eb-a5b7-5afe3df4
[Desktop-packages] [Bug 1771749] NetworkManager.conf.txt
apport information ** Attachment added: "NetworkManager.conf.txt" https://bugs.launchpad.net/bugs/1771749/+attachment/5140831/+files/NetworkManager.conf.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1771749 Title: Ethernet connection lost after few minutes since starting Status in linux package in Ubuntu: Confirmed Status in network-manager package in Ubuntu: New Bug description: This is the same bug I notified at Bug #1770848 but with a more precise selection of (what I think it is) the package affected and a better description. I made a few days ago a fresh install of the Kubuntu 18.04 LTS and it is most everything Ok, but -I think that- the network-manager has a problem. In the last LTS version, Kubuntu 16.04, nor in any Linux version if I remember well, I never lost connection through Ethernet (the only Internet connection with our desktop PC), but the Bionic Beaver loses the connection every now and then, perhaps within few minutes or hours, but several times per day. When the connection is lost, I note that it disappears any info even mention to any network into the network window and the network manager icon becomes red color. Not matter if I unplug and then plug the ethernet cable again, the ethernet connection is not longer detected and only restarting the PC makes the connection to work again. Incidentally, I also have noticed with this version of Kubuntu 18.04 that in my laptop there is also now a similar problem with the scanner: If I plug it in some USB port of the laptop once Kubuntu 18.04 is already running, it's not detected by Xsane. I have to plug it in before than pressing the power button or at the time of starting the OS, for the scanner to be detected by the scanning program (and then only works with Xsane, not if I use Simple Scan or Skanlite, even when it works under Xsane), as I said in the Bug #1771525 and, evenly, if I unplug the scanner cable from the USB port it is not detected anymore when plugging it again, and only restarting the laptop makes it to be detected. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: network-manager 1.10.6-2ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 CurrentDesktop: KDE Date: Thu May 17 08:24:23 2018 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2018-05-11 (5 days ago) InstallationMedia: Kubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) IpRoute: default via 192.168.1.1 dev enp0s7 proto static metric 100 169.254.0.0/16 dev enp0s7 scope link metric 1000 192.168.1.0/24 dev enp0s7 proto kernel scope link src 192.168.1.3 metric 100 IwConfig: enp0s7no wireless extensions. lono wireless extensions. NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true PciNetwork: RfKill: SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) nmcli-con: NAME UUID TYPE TIMESTAMP TIMESTAMP-REAL AUTOCONNECT AUTOCONNECT-PRIORITY READONLY DBUS-PATH ACTIVE DEVICE STATE ACTIVE-PATH SLAVE Conexión cableada 1 1cc37db8-0db8-3887-acf2-59fbbcd0cb1c ethernet 1526538083 jue 17 may 2018 08:21:23 CEST yes 4294967196 no/org/freedesktop/NetworkManager/Settings/1 yes enp0s7 activated /org/freedesktop/NetworkManager/ActiveConnection/1 -- nmcli-dev: DEVICE TYPE STATE DBUS-PATH CONNECTION CON-UUID CON-PATH enp0s7 ethernet connected /org/freedesktop/NetworkManager/Devices/2 Conexión cableada 1 1cc37db8-0db8-3887-acf2-59fbbcd0cb1c /org/freedesktop/NetworkManager/ActiveConnection/1 lo loopback unmanaged /org/freedesktop/NetworkManager/Devices/1 -- ---- nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.10.6 connected started full enabled enabled enabled enabled enabled --- ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: nosotros 1116 F pulseaudio /dev/snd/controlC1: nosotros 1116 F pulseaudio CurrentDesktop: KDE DistroRelease: Ubuntu 18.04 HibernationDevice: RESUME=UUID=bb1531db-e7c0-48eb-a5b7-5afe3d
[Desktop-packages] [Bug 1771749] WifiSyslog.txt
apport information ** Attachment added: "WifiSyslog.txt" https://bugs.launchpad.net/bugs/1771749/+attachment/5140838/+files/WifiSyslog.txt ** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1771749 Title: Ethernet connection lost after few minutes since starting Status in linux package in Ubuntu: Confirmed Status in network-manager package in Ubuntu: New Bug description: This is the same bug I notified at Bug #1770848 but with a more precise selection of (what I think it is) the package affected and a better description. I made a few days ago a fresh install of the Kubuntu 18.04 LTS and it is most everything Ok, but -I think that- the network-manager has a problem. In the last LTS version, Kubuntu 16.04, nor in any Linux version if I remember well, I never lost connection through Ethernet (the only Internet connection with our desktop PC), but the Bionic Beaver loses the connection every now and then, perhaps within few minutes or hours, but several times per day. When the connection is lost, I note that it disappears any info even mention to any network into the network window and the network manager icon becomes red color. Not matter if I unplug and then plug the ethernet cable again, the ethernet connection is not longer detected and only restarting the PC makes the connection to work again. Incidentally, I also have noticed with this version of Kubuntu 18.04 that in my laptop there is also now a similar problem with the scanner: If I plug it in some USB port of the laptop once Kubuntu 18.04 is already running, it's not detected by Xsane. I have to plug it in before than pressing the power button or at the time of starting the OS, for the scanner to be detected by the scanning program (and then only works with Xsane, not if I use Simple Scan or Skanlite, even when it works under Xsane), as I said in the Bug #1771525 and, evenly, if I unplug the scanner cable from the USB port it is not detected anymore when plugging it again, and only restarting the laptop makes it to be detected. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: network-manager 1.10.6-2ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 CurrentDesktop: KDE Date: Thu May 17 08:24:23 2018 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2018-05-11 (5 days ago) InstallationMedia: Kubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) IpRoute: default via 192.168.1.1 dev enp0s7 proto static metric 100 169.254.0.0/16 dev enp0s7 scope link metric 1000 192.168.1.0/24 dev enp0s7 proto kernel scope link src 192.168.1.3 metric 100 IwConfig: enp0s7no wireless extensions. lono wireless extensions. NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true PciNetwork: RfKill: SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) nmcli-con: NAME UUID TYPE TIMESTAMP TIMESTAMP-REAL AUTOCONNECT AUTOCONNECT-PRIORITY READONLY DBUS-PATH ACTIVE DEVICE STATE ACTIVE-PATH SLAVE Conexión cableada 1 1cc37db8-0db8-3887-acf2-59fbbcd0cb1c ethernet 1526538083 jue 17 may 2018 08:21:23 CEST yes 4294967196 no/org/freedesktop/NetworkManager/Settings/1 yes enp0s7 activated /org/freedesktop/NetworkManager/ActiveConnection/1 -- nmcli-dev: DEVICE TYPE STATE DBUS-PATH CONNECTION CON-UUID CON-PATH enp0s7 ethernet connected /org/freedesktop/NetworkManager/Devices/2 Conexión cableada 1 1cc37db8-0db8-3887-acf2-59fbbcd0cb1c /org/freedesktop/NetworkManager/ActiveConnection/1 lo loopback unmanaged /org/freedesktop/NetworkManager/Devices/1 -- ---- nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.10.6 connected started full enabled enabled enabled enabled enabled --- ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: nosotros 1116 F pulseaudio /dev/snd/controlC1: nosotros 1116 F pulseaudio CurrentDesktop: KDE DistroRelease: Ubuntu 18.04 Hibernati
[Desktop-packages] [Bug 1771749] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/1771749/+attachment/5140835/+files/ProcModules.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1771749 Title: Ethernet connection lost after few minutes since starting Status in linux package in Ubuntu: Confirmed Status in network-manager package in Ubuntu: New Bug description: This is the same bug I notified at Bug #1770848 but with a more precise selection of (what I think it is) the package affected and a better description. I made a few days ago a fresh install of the Kubuntu 18.04 LTS and it is most everything Ok, but -I think that- the network-manager has a problem. In the last LTS version, Kubuntu 16.04, nor in any Linux version if I remember well, I never lost connection through Ethernet (the only Internet connection with our desktop PC), but the Bionic Beaver loses the connection every now and then, perhaps within few minutes or hours, but several times per day. When the connection is lost, I note that it disappears any info even mention to any network into the network window and the network manager icon becomes red color. Not matter if I unplug and then plug the ethernet cable again, the ethernet connection is not longer detected and only restarting the PC makes the connection to work again. Incidentally, I also have noticed with this version of Kubuntu 18.04 that in my laptop there is also now a similar problem with the scanner: If I plug it in some USB port of the laptop once Kubuntu 18.04 is already running, it's not detected by Xsane. I have to plug it in before than pressing the power button or at the time of starting the OS, for the scanner to be detected by the scanning program (and then only works with Xsane, not if I use Simple Scan or Skanlite, even when it works under Xsane), as I said in the Bug #1771525 and, evenly, if I unplug the scanner cable from the USB port it is not detected anymore when plugging it again, and only restarting the laptop makes it to be detected. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: network-manager 1.10.6-2ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 CurrentDesktop: KDE Date: Thu May 17 08:24:23 2018 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2018-05-11 (5 days ago) InstallationMedia: Kubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) IpRoute: default via 192.168.1.1 dev enp0s7 proto static metric 100 169.254.0.0/16 dev enp0s7 scope link metric 1000 192.168.1.0/24 dev enp0s7 proto kernel scope link src 192.168.1.3 metric 100 IwConfig: enp0s7no wireless extensions. lono wireless extensions. NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true PciNetwork: RfKill: SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) nmcli-con: NAME UUID TYPE TIMESTAMP TIMESTAMP-REAL AUTOCONNECT AUTOCONNECT-PRIORITY READONLY DBUS-PATH ACTIVE DEVICE STATE ACTIVE-PATH SLAVE Conexión cableada 1 1cc37db8-0db8-3887-acf2-59fbbcd0cb1c ethernet 1526538083 jue 17 may 2018 08:21:23 CEST yes 4294967196 no/org/freedesktop/NetworkManager/Settings/1 yes enp0s7 activated /org/freedesktop/NetworkManager/ActiveConnection/1 -- nmcli-dev: DEVICE TYPE STATE DBUS-PATH CONNECTION CON-UUID CON-PATH enp0s7 ethernet connected /org/freedesktop/NetworkManager/Devices/2 Conexión cableada 1 1cc37db8-0db8-3887-acf2-59fbbcd0cb1c /org/freedesktop/NetworkManager/ActiveConnection/1 lo loopback unmanaged /org/freedesktop/NetworkManager/Devices/1 -- ---- nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.10.6 connected started full enabled enabled enabled enabled enabled --- ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: nosotros 1116 F pulseaudio /dev/snd/controlC1: nosotros 1116 F pulseaudio CurrentDesktop: KDE DistroRelease: Ubuntu 18.04 HibernationDevice: RESUME=UUID=bb1531db-e7c0-48eb-a5b7-5afe3df47ba3 Ifupdow
[Desktop-packages] [Bug 1771749] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/1771749/+attachment/5140837/+files/UdevDb.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1771749 Title: Ethernet connection lost after few minutes since starting Status in linux package in Ubuntu: Confirmed Status in network-manager package in Ubuntu: New Bug description: This is the same bug I notified at Bug #1770848 but with a more precise selection of (what I think it is) the package affected and a better description. I made a few days ago a fresh install of the Kubuntu 18.04 LTS and it is most everything Ok, but -I think that- the network-manager has a problem. In the last LTS version, Kubuntu 16.04, nor in any Linux version if I remember well, I never lost connection through Ethernet (the only Internet connection with our desktop PC), but the Bionic Beaver loses the connection every now and then, perhaps within few minutes or hours, but several times per day. When the connection is lost, I note that it disappears any info even mention to any network into the network window and the network manager icon becomes red color. Not matter if I unplug and then plug the ethernet cable again, the ethernet connection is not longer detected and only restarting the PC makes the connection to work again. Incidentally, I also have noticed with this version of Kubuntu 18.04 that in my laptop there is also now a similar problem with the scanner: If I plug it in some USB port of the laptop once Kubuntu 18.04 is already running, it's not detected by Xsane. I have to plug it in before than pressing the power button or at the time of starting the OS, for the scanner to be detected by the scanning program (and then only works with Xsane, not if I use Simple Scan or Skanlite, even when it works under Xsane), as I said in the Bug #1771525 and, evenly, if I unplug the scanner cable from the USB port it is not detected anymore when plugging it again, and only restarting the laptop makes it to be detected. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: network-manager 1.10.6-2ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 CurrentDesktop: KDE Date: Thu May 17 08:24:23 2018 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2018-05-11 (5 days ago) InstallationMedia: Kubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) IpRoute: default via 192.168.1.1 dev enp0s7 proto static metric 100 169.254.0.0/16 dev enp0s7 scope link metric 1000 192.168.1.0/24 dev enp0s7 proto kernel scope link src 192.168.1.3 metric 100 IwConfig: enp0s7no wireless extensions. lono wireless extensions. NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true PciNetwork: RfKill: SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) nmcli-con: NAME UUID TYPE TIMESTAMP TIMESTAMP-REAL AUTOCONNECT AUTOCONNECT-PRIORITY READONLY DBUS-PATH ACTIVE DEVICE STATE ACTIVE-PATH SLAVE Conexión cableada 1 1cc37db8-0db8-3887-acf2-59fbbcd0cb1c ethernet 1526538083 jue 17 may 2018 08:21:23 CEST yes 4294967196 no/org/freedesktop/NetworkManager/Settings/1 yes enp0s7 activated /org/freedesktop/NetworkManager/ActiveConnection/1 -- nmcli-dev: DEVICE TYPE STATE DBUS-PATH CONNECTION CON-UUID CON-PATH enp0s7 ethernet connected /org/freedesktop/NetworkManager/Devices/2 Conexión cableada 1 1cc37db8-0db8-3887-acf2-59fbbcd0cb1c /org/freedesktop/NetworkManager/ActiveConnection/1 lo loopback unmanaged /org/freedesktop/NetworkManager/Devices/1 -- ---- nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.10.6 connected started full enabled enabled enabled enabled enabled --- ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: nosotros 1116 F pulseaudio /dev/snd/controlC1: nosotros 1116 F pulseaudio CurrentDesktop: KDE DistroRelease: Ubuntu 18.04 HibernationDevice: RESUME=UUID=bb1531db-e7c0-48eb-a5b7-5afe3df47ba3 IfupdownConfig:
[Desktop-packages] [Bug 1771749] PulseList.txt
apport information ** Attachment added: "PulseList.txt" https://bugs.launchpad.net/bugs/1771749/+attachment/5140836/+files/PulseList.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1771749 Title: Ethernet connection lost after few minutes since starting Status in linux package in Ubuntu: Confirmed Status in network-manager package in Ubuntu: New Bug description: This is the same bug I notified at Bug #1770848 but with a more precise selection of (what I think it is) the package affected and a better description. I made a few days ago a fresh install of the Kubuntu 18.04 LTS and it is most everything Ok, but -I think that- the network-manager has a problem. In the last LTS version, Kubuntu 16.04, nor in any Linux version if I remember well, I never lost connection through Ethernet (the only Internet connection with our desktop PC), but the Bionic Beaver loses the connection every now and then, perhaps within few minutes or hours, but several times per day. When the connection is lost, I note that it disappears any info even mention to any network into the network window and the network manager icon becomes red color. Not matter if I unplug and then plug the ethernet cable again, the ethernet connection is not longer detected and only restarting the PC makes the connection to work again. Incidentally, I also have noticed with this version of Kubuntu 18.04 that in my laptop there is also now a similar problem with the scanner: If I plug it in some USB port of the laptop once Kubuntu 18.04 is already running, it's not detected by Xsane. I have to plug it in before than pressing the power button or at the time of starting the OS, for the scanner to be detected by the scanning program (and then only works with Xsane, not if I use Simple Scan or Skanlite, even when it works under Xsane), as I said in the Bug #1771525 and, evenly, if I unplug the scanner cable from the USB port it is not detected anymore when plugging it again, and only restarting the laptop makes it to be detected. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: network-manager 1.10.6-2ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 CurrentDesktop: KDE Date: Thu May 17 08:24:23 2018 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2018-05-11 (5 days ago) InstallationMedia: Kubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) IpRoute: default via 192.168.1.1 dev enp0s7 proto static metric 100 169.254.0.0/16 dev enp0s7 scope link metric 1000 192.168.1.0/24 dev enp0s7 proto kernel scope link src 192.168.1.3 metric 100 IwConfig: enp0s7no wireless extensions. lono wireless extensions. NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true PciNetwork: RfKill: SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) nmcli-con: NAME UUID TYPE TIMESTAMP TIMESTAMP-REAL AUTOCONNECT AUTOCONNECT-PRIORITY READONLY DBUS-PATH ACTIVE DEVICE STATE ACTIVE-PATH SLAVE Conexión cableada 1 1cc37db8-0db8-3887-acf2-59fbbcd0cb1c ethernet 1526538083 jue 17 may 2018 08:21:23 CEST yes 4294967196 no/org/freedesktop/NetworkManager/Settings/1 yes enp0s7 activated /org/freedesktop/NetworkManager/ActiveConnection/1 -- nmcli-dev: DEVICE TYPE STATE DBUS-PATH CONNECTION CON-UUID CON-PATH enp0s7 ethernet connected /org/freedesktop/NetworkManager/Devices/2 Conexión cableada 1 1cc37db8-0db8-3887-acf2-59fbbcd0cb1c /org/freedesktop/NetworkManager/ActiveConnection/1 lo loopback unmanaged /org/freedesktop/NetworkManager/Devices/1 -- ---- nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.10.6 connected started full enabled enabled enabled enabled enabled --- ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: nosotros 1116 F pulseaudio /dev/snd/controlC1: nosotros 1116 F pulseaudio CurrentDesktop: KDE DistroRelease: Ubuntu 18.04 HibernationDevice: RESUME=UUID=bb1531db-e7c0-48eb-a5b7-5afe3df47ba3 IfupdownCon
Re: [Desktop-packages] [Bug 1759468] Re: gnome-control-center (11) gtk_style_context_clear_property_cache → gtk_css_widget_node_update_style → gtk_css_node_ensure_style → gtk_css_node_ensure_style → g
Yes. The other part is not required in 3.28. Il gio 17 mag 2018, 03:31 Sebastien Bacher ha scritto: > @andyrock, is https://gitlab.gnome.org/GNOME/gnome-control- > center/merge_requests/49/diffs the correct fix for that segfault? it > seems only half of the change from master, is that enough? > > -- > You received this bug notification because you are a bug assignee. > https://bugs.launchpad.net/bugs/1759468 > > Title: > gnome-control-center (11) gtk_style_context_clear_property_cache → > gtk_css_widget_node_update_style → gtk_css_node_ensure_style → > gtk_css_node_ensure_style → gtk_css_node_validate_internal > > Status in gnome-control-center package in Ubuntu: > In Progress > Status in gtk+3.0 package in Ubuntu: > Fix Released > > Bug description: > * Impact > gnome-control-center sometimes hits a segfault > > * Test case > - Check if the e.u.c reports stop with the new version > > or > > - Open GNOME Control Center > - Go to Devices->Display panel > - Close the window > - Open GNOME Control Center again (in overview mode) > > the settings should open without error > > * Regression potential > check the panels can be opened without error and that switching between > them works as well > > -- > > The Ubuntu Error Tracker has been receiving reports about a problem > regarding gnome-control-center. This problem was most recently seen with > package version 1:3.28.0-0ubuntu2, the problem page at > https://errors.ubuntu.com/problem/6b1f4dd86167bf5eb53ddca8469b5084208ddd22 > contains more details, including versions of packages affected, stacktrace > or traceback, and individual crash reports. > If you do not have access to the Ubuntu Error Tracker and are a software > developer, you can request it at http://forms.canonical.com/reports/. > > To manage notifications about this bug go to: > > https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1759468/+subscriptions > > Launchpad-Notification-Type: bug > Launchpad-Bug: distribution=ubuntu; sourcepackage=gnome-control-center; > component=main; status=In Progress; importance=High; assignee= > andrea.azzar...@canonical.com; > Launchpad-Bug: distribution=ubuntu; sourcepackage=gtk+3.0; component=main; > status=Fix Released; importance=High; assignee= > andrea.azzar...@canonical.com; > Launchpad-Bug-Tags: artful bionic patch > Launchpad-Bug-Information-Type: Public > Launchpad-Bug-Private: no > Launchpad-Bug-Security-Vulnerability: no > Launchpad-Bug-Commenters: azzar1 crichton janitor jbicha seb128 > whoopsie-daisy-bug-bridge > Launchpad-Bug-Reporter: errors.ubuntu.com bug bridge > (whoopsie-daisy-bug-bridge) > Launchpad-Bug-Modifier: Sebastien Bacher (seb128) > Launchpad-Message-Rationale: Assignee > Launchpad-Message-For: azzar1 > -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1759468 Title: gnome-control-center (11) gtk_style_context_clear_property_cache → gtk_css_widget_node_update_style → gtk_css_node_ensure_style → gtk_css_node_ensure_style → gtk_css_node_validate_internal Status in gnome-control-center package in Ubuntu: In Progress Status in gtk+3.0 package in Ubuntu: Fix Released Bug description: * Impact gnome-control-center sometimes hits a segfault * Test case - Check if the e.u.c reports stop with the new version or - Open GNOME Control Center - Go to Devices->Display panel - Close the window - Open GNOME Control Center again (in overview mode) the settings should open without error * Regression potential check the panels can be opened without error and that switching between them works as well -- The Ubuntu Error Tracker has been receiving reports about a problem regarding gnome-control-center. This problem was most recently seen with package version 1:3.28.0-0ubuntu2, the problem page at https://errors.ubuntu.com/problem/6b1f4dd86167bf5eb53ddca8469b5084208ddd22 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1759468/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1771818] Re: 'Unable to install "GNOME Characters": cannot perform the following tasks' but it installs anyway
** Attachment added: "Screenshot from 2018-05-17 14-28-45.png" https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1771818/+attachment/5140844/+files/Screenshot%20from%202018-05-17%2014-28-45.png -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-software in Ubuntu. https://bugs.launchpad.net/bugs/1771818 Title: 'Unable to install "GNOME Characters": cannot perform the following tasks' but it installs anyway Status in gnome-software package in Ubuntu: New Bug description: Hit install for GNOME Characters (stable) and got the popup in the title above but it runs fine... ``` $ snap info gnome-characters tracking: stable refreshed: 2018-04-27T02:36:32+01:00 installed: 3.28.0 (86) 13MB - $ snap version snap2.32.8+18.04 snapd 2.32.8+18.04 series 16 ubuntu 18.04 kernel 4.15.0-20-generic $ snap info core tracking: beta refreshed: 2018-05-11T15:51:12+01:00 installed: 16-2.32.8(4650) 90MB core ``` ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-software 3.28.1-0ubuntu4 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 CurrentDesktop: communitheme:ubuntu:GNOME Date: Thu May 17 14:25:14 2018 InstallationDate: Installed on 2017-08-03 (286 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) InstalledPlugins: gnome-software-plugin-flatpak 3.28.1-0ubuntu4 gnome-software-plugin-limba N/A gnome-software-plugin-snap3.28.1-0ubuntu4 SourcePackage: gnome-software UpgradeStatus: Upgraded to bionic on 2018-04-22 (25 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1771818/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1771818] [NEW] 'Unable to install "GNOME Characters": cannot perform the following tasks' but it installs anyway
Public bug reported: Hit install for GNOME Characters (stable) and got the popup in the title above but it runs fine... ``` $ snap info gnome-characters tracking: stable refreshed: 2018-04-27T02:36:32+01:00 installed: 3.28.0 (86) 13MB - $ snap version snap2.32.8+18.04 snapd 2.32.8+18.04 series 16 ubuntu 18.04 kernel 4.15.0-20-generic $ snap info core tracking: beta refreshed: 2018-05-11T15:51:12+01:00 installed: 16-2.32.8(4650) 90MB core ``` ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-software 3.28.1-0ubuntu4 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 CurrentDesktop: communitheme:ubuntu:GNOME Date: Thu May 17 14:25:14 2018 InstallationDate: Installed on 2017-08-03 (286 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) InstalledPlugins: gnome-software-plugin-flatpak 3.28.1-0ubuntu4 gnome-software-plugin-limba N/A gnome-software-plugin-snap3.28.1-0ubuntu4 SourcePackage: gnome-software UpgradeStatus: Upgraded to bionic on 2018-04-22 (25 days ago) ** Affects: gnome-software (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic wayland-session -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-software in Ubuntu. https://bugs.launchpad.net/bugs/1771818 Title: 'Unable to install "GNOME Characters": cannot perform the following tasks' but it installs anyway Status in gnome-software package in Ubuntu: New Bug description: Hit install for GNOME Characters (stable) and got the popup in the title above but it runs fine... ``` $ snap info gnome-characters tracking: stable refreshed: 2018-04-27T02:36:32+01:00 installed: 3.28.0 (86) 13MB - $ snap version snap2.32.8+18.04 snapd 2.32.8+18.04 series 16 ubuntu 18.04 kernel 4.15.0-20-generic $ snap info core tracking: beta refreshed: 2018-05-11T15:51:12+01:00 installed: 16-2.32.8(4650) 90MB core ``` ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-software 3.28.1-0ubuntu4 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 CurrentDesktop: communitheme:ubuntu:GNOME Date: Thu May 17 14:25:14 2018 InstallationDate: Installed on 2017-08-03 (286 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) InstalledPlugins: gnome-software-plugin-flatpak 3.28.1-0ubuntu4 gnome-software-plugin-limba N/A gnome-software-plugin-snap3.28.1-0ubuntu4 SourcePackage: gnome-software UpgradeStatus: Upgraded to bionic on 2018-04-22 (25 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1771818/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1768779] Re: Snap channel selection list not scrollable
I'm not able to test if it scroll or not as the other bug (#1768794) was fixed and now I see only 4 entries. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-software in Ubuntu. https://bugs.launchpad.net/bugs/1768779 Title: Snap channel selection list not scrollable Status in gnome-software package in Ubuntu: Fix Released Status in gnome-software source package in Xenial: Fix Committed Status in gnome-software source package in Bionic: Fix Committed Status in gnome-software source package in Cosmic: Fix Released Bug description: [Impact] Snaps with many channels/branches (e.g. communitheme) make the channel selector too large - it should use a scrollable window if there are many. [Test Case] 1. Search for ”communitheme” in the store 2. Open ”communitheme” result 3. Click on the channel selection button 4. You will see a popup with loong list of channels 5. Try to scroll to see more entries Expected result: You can scroll the list What happen instead: You cannot scroll the list [Regression Potential] Solution is to use a GtkScrolledWindow for the list. Could cause other UI bugs to occur. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1768779/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1771242] Re: Update gnome-desktop3 to 3.28.2
So Ubuntu 18.04 will not receive gnome 3.28.2? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-desktop3 in Ubuntu. https://bugs.launchpad.net/bugs/1771242 Title: Update gnome-desktop3 to 3.28.2 Status in gnome-desktop3 package in Ubuntu: Fix Released Status in gnome-desktop3 source package in Bionic: In Progress Bug description: Impact == This updates the GNOME version number reported in Settings > Details > About to 3.28.2 This is the final scheduled point release for GNOME 3.28. Since we're updating most of the other GNOME packages to 3.28.2, it's appropriate to do this update too. (We might hold this update in -proposed a bit until we update say gnome-shell to 3.28.2) Tne new version also fixes a memory leak and includes some translation fixes. https://git.gnome.org/browse/gnome-desktop/tree/NEWS?h=gnome-3-28 https://git.gnome.org/browse/gnome-desktop/log?h=gnome-3-28 Test Case = From Ubuntu 18.04 LTS, open the Settings app. Navigate to Details > About The GNOME version number should say 3.28.2 Regression Potential There is a micro-release exception for GNOME: https://wiki.ubuntu.com/StableReleaseUpdates#GNOME To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-desktop3/+bug/1771242/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1698593] Re: [Blade, Realtek ALC298, Black Mic, Left] No sound at all
Use the following parameter... options snd-hda-intel model=laptop-dmic -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1698593 Title: [Blade, Realtek ALC298, Black Mic, Left] No sound at all Status in alsa-driver package in Ubuntu: Confirmed Bug description: I'm trying to get the mic from the combo jack on my Razer Blade working. Headphones are functioning perfectly, but the mic seems to be picking up on random data, unrelated to sound output or my surroundings. I know the jack is working as I dual-boot Windows, and it works great there. I've added the `options snd-hda-intel model=laptop-dmic` line as recommended in some other threads, and tried setting pin 0x18 to mic using hdajackretask, but it hasn't fixed it or made any difference. ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.10.0-22.24-generic 4.10.15 Uname: Linux 4.10.0-22-generic x86_64 ApportVersion: 2.20.4-0ubuntu4.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC0D0c: octy 1971 F...m pulseaudio /dev/snd/pcmC0D0p: octy 1971 F...m pulseaudio /dev/snd/controlC0: octy 1971 F pulseaudio CurrentDesktop: X-Cinnamon Date: Sat Jun 17 15:21:41 2017 EcryptfsInUse: Yes InstallationDate: Installed on 2017-04-06 (72 days ago) InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaRecordingTest: ALSA recording test through plughw:PCH failed Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC0D0c: octy 1971 F...m pulseaudio /dev/snd/pcmC0D0p: octy 1971 F...m pulseaudio /dev/snd/controlC0: octy 1971 F pulseaudio Symptom_Jack: Black Mic, Left Symptom_Type: No sound at all Title: [Blade, Realtek ALC298, Black Mic, Left] No sound at all UpgradeStatus: Upgraded to zesty on 2017-04-15 (63 days ago) dmi.bios.date: 01/10/2017 dmi.bios.vendor: Razer dmi.bios.version: 1.00 dmi.board.name: Razer dmi.board.vendor: Razer dmi.chassis.type: 9 dmi.chassis.vendor: Razer dmi.modalias: dmi:bvnRazer:bvr1.00:bd01/10/2017:svnRazer:pnBlade:pvr6.06:rvnRazer:rnRazer:rvr:cvnRazer:ct9:cvr: dmi.product.name: Blade dmi.product.version: 6.06 dmi.sys.vendor: Razer mtime.conffile..etc.modprobe.d.alsa-base.conf: 2017-06-17T15:06:35.753276 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1698593/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1771242] Re: Update gnome-desktop3 to 3.28.2
> So Ubuntu 18.04 will not receive gnome 3.28.2? Ubuntu 18.04 LTS will get GNOME 3.28.2. This bug report is part of that process. :) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-desktop3 in Ubuntu. https://bugs.launchpad.net/bugs/1771242 Title: Update gnome-desktop3 to 3.28.2 Status in gnome-desktop3 package in Ubuntu: Fix Released Status in gnome-desktop3 source package in Bionic: In Progress Bug description: Impact == This updates the GNOME version number reported in Settings > Details > About to 3.28.2 This is the final scheduled point release for GNOME 3.28. Since we're updating most of the other GNOME packages to 3.28.2, it's appropriate to do this update too. (We might hold this update in -proposed a bit until we update say gnome-shell to 3.28.2) Tne new version also fixes a memory leak and includes some translation fixes. https://git.gnome.org/browse/gnome-desktop/tree/NEWS?h=gnome-3-28 https://git.gnome.org/browse/gnome-desktop/log?h=gnome-3-28 Test Case = From Ubuntu 18.04 LTS, open the Settings app. Navigate to Details > About The GNOME version number should say 3.28.2 Regression Potential There is a micro-release exception for GNOME: https://wiki.ubuntu.com/StableReleaseUpdates#GNOME To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-desktop3/+bug/1771242/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1070873] Re: kde-telepathy, impossible to connect to gmail accounts
I have discovered the cause for this. You are using a proxy with an autoconfiguration URL (PAC script) which has got a syntax error in it (as far as WebKit is concerned) When you run the add account it calls signon-ui and it segfaults because of this. If you use konqueror you may also experience problems. In my case, it takes a very long time to load pages, like almost a minute long. If you can, temporarily disable your proxy, or if you cannot connect without proxy, try manually setting the address of the proxy (not the PAC stript), for the duration of adding the account. Once the account has been added, signon-ui isn't needed, and the proxy settings can be re-instated. ** Attachment added: "backtrace" https://bugs.launchpad.net/ubuntu/+source/meta-kde-telepathy/+bug/1070873/+attachment/5140871/+files/bt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to signon-ui in Ubuntu. https://bugs.launchpad.net/bugs/1070873 Title: kde-telepathy, impossible to connect to gmail accounts Status in meta-kde-telepathy package in Ubuntu: Confirmed Status in signon-ui package in Ubuntu: Confirmed Bug description: Im running ubuntu 12.10 quantal and i have installed kde, when running kde-telepathy i have added a gmail account, and after entering the password it has revealed impossible to connect to it, it always says that the password is wrong when that is false. When using empathy, i have removed the gmail account and have added it again, now appears a XMLL window asking ubuntu permission to conenct to it, and now i was able to conenct to the gmail account. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/meta-kde-telepathy/+bug/1070873/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1556960] Re: Cannot install nvidia driver using software-properties-gtk. package nvidia-361 361.28-0ubuntu1 failed to install/upgrade: subprocess installed post-installation sc
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: nvidia-graphics-drivers-361 (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-graphics-drivers-361 in Ubuntu. https://bugs.launchpad.net/bugs/1556960 Title: Cannot install nvidia driver using software-properties-gtk. package nvidia-361 361.28-0ubuntu1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 255 Status in nvidia-graphics-drivers-361 package in Ubuntu: Confirmed Bug description: In trying a workaround for https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1547077 tried once again to install nVidia proprietary driver using software-properties- gtk. Observed: crash report window appears, software-properties-gtk appears to cancel the installation and rollback. This is at least the third time and bug report in a few weeks (not trying to complain, just reporting), details in https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1547077. especially https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1547077/comments/41 https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1547077/comments/42 The glyph bug impact the very process of reporting this as the semi- workaround I use does not work for everything. For example, there's currently no workaround for the context menu in firefox. Thank you for your attention. ProblemType: Package DistroRelease: Ubuntu 16.04 Package: nvidia-361 361.28-0ubuntu1 ProcVersionSignature: Ubuntu 4.4.0-12.28-generic 4.4.4 Uname: Linux 4.4.0-12-generic x86_64 ApportVersion: 2.20-0ubuntu3 Architecture: amd64 Date: Mon Mar 14 14:48:59 2016 ErrorMessage: subprocess installed post-installation script returned error exit status 255 InstallationDate: Installed on 2016-02-03 (39 days ago) InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160203) RelatedPackageVersions: dpkg 1.18.4ubuntu1 apt 1.2.4 SourcePackage: nvidia-graphics-drivers-361 Title: package nvidia-361 361.28-0ubuntu1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 255 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-361/+bug/1556960/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1771839] [NEW] keyboard
Public bug reported: The keyboard is desconfigurated for spanish. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.13.0-41.46~16.04.1-generic 4.13.16 Uname: Linux 4.13.0-41-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.17 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true Date: Thu May 17 10:03:40 2018 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu GraphicsCard: Intel Corporation Sky Lake Integrated Graphics [8086:1912] (rev 06) (prog-if 00 [VGA controller]) Subsystem: Dell Skylake Integrated Graphics [1028:06fb] InstallationDate: Installed on 2017-04-21 (390 days ago) InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215.2) MachineType: Dell Inc. Vostro 3250 ProcEnviron: LANGUAGE=es_MX:es PATH=(custom, no user) LANG=es_MX.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-41-generic.efi.signed root=UUID=dc72dcd9-c240-4235-8887-e0f5bbeb954c ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/07/2017 dmi.bios.vendor: Dell Inc. dmi.bios.version: 3.5.2 dmi.board.name: 0J4NFV dmi.board.vendor: Dell Inc. dmi.board.version: A01 dmi.chassis.type: 3 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnDellInc.:bvr3.5.2:bd12/07/2017:svnDellInc.:pnVostro3250:pvrX00:rvnDellInc.:rn0J4NFV:rvrA01:cvnDellInc.:ct3:cvrNotSpecified: dmi.product.family: Vostro dmi.product.name: Vostro 3250 dmi.product.version: X00 dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.12.3+16.04.20180221-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.83-1~16.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.8-0ubuntu0~16.04.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.8-0ubuntu0~16.04.1 version.xserver-xorg-core: xserver-xorg-core N/A version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A xserver.bootTime: Thu May 17 08:46:00 2018 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: OutputDP-1 HDMI-1 xserver.version: 2:1.19.5-0ubuntu2~16.04.1 xserver.video_driver: modeset ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug compiz-0.9 ubuntu xenial -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1771839 Title: keyboard Status in xorg package in Ubuntu: New Bug description: The keyboard is desconfigurated for spanish. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.13.0-41.46~16.04.1-generic 4.13.16 Uname: Linux 4.13.0-41-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.17 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true Date: Thu May 17 10:03:40 2018 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu GraphicsCard: Intel Corporation Sky Lake Integrated Graphics [8086:1912] (rev 06) (prog-if 00 [VGA controller]) Subsystem: Dell Skylake Integrated Graphics [1028:06fb] InstallationDate: Installed on 2017-04-21 (390 days ago) InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215.2) MachineType: Dell Inc. Vostro 3250 ProcEnviron: LANGUAGE=es_MX:es PATH=(custom, no user) LANG=es_MX.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-41-generic.efi.signed root=UUID=dc72dcd9-c240-4235-8887-e0f5bbeb954c ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/07/2017 dmi.bios.vendor: Dell Inc. dmi.bios.version: 3.5.2 dmi.board.name: 0J4NFV dmi.board.vendor: Dell Inc. dmi.board.version: A01 dmi.chassis.type: 3 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnDellInc.:bvr3.5.2:bd12/07/2017:svnDellInc.:pnVostro3250:pvrX00:rvnDellInc.:rn0J4NFV:rvrA01:cvnDellInc.:ct3:cvrNotSpecified: dmi.product.family: Vostro dmi.product.name: Vostro 3250 dmi.product.version: X00 dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.1
[Desktop-packages] [Bug 1070873] Re: kde-telepathy, impossible to connect to gmail accounts
ok scratch the part about the syntax error as I have fixed my PAC file. which leaves... you can encounter this problem if you have a proxy server configured. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to signon-ui in Ubuntu. https://bugs.launchpad.net/bugs/1070873 Title: kde-telepathy, impossible to connect to gmail accounts Status in meta-kde-telepathy package in Ubuntu: Confirmed Status in signon-ui package in Ubuntu: Confirmed Bug description: Im running ubuntu 12.10 quantal and i have installed kde, when running kde-telepathy i have added a gmail account, and after entering the password it has revealed impossible to connect to it, it always says that the password is wrong when that is false. When using empathy, i have removed the gmail account and have added it again, now appears a XMLL window asking ubuntu permission to conenct to it, and now i was able to conenct to the gmail account. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/meta-kde-telepathy/+bug/1070873/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1771847] Re: chromium-browser.svg icon is outdated
This also affects the snap, because the snap uses the SVG icon. ** Tags added: snap -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/1771847 Title: chromium-browser.svg icon is outdated Status in chromium-browser package in Ubuntu: In Progress Bug description: The chromium-browser package installs an SVG icon (/usr/share/icons/hicolor/scalable/apps/chromium-browser.svg) - that file comes from the debian/ directory, not from the upstream tarballs, and as such is outdated in comparison with the PNG icons at various sizes that come from the tarballs. I wasn't able to find a recent version of the chromium icon in SVG form, so that icon should be removed. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1771847/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1771847] [NEW] chromium-browser.svg icon is outdated
Public bug reported: The chromium-browser package installs an SVG icon (/usr/share/icons/hicolor/scalable/apps/chromium-browser.svg) - that file comes from the debian/ directory, not from the upstream tarballs, and as such is outdated in comparison with the PNG icons at various sizes that come from the tarballs. I wasn't able to find a recent version of the chromium icon in SVG form, so that icon should be removed. ** Affects: chromium-browser (Ubuntu) Importance: Low Assignee: Olivier Tilloy (osomon) Status: In Progress ** Tags: snap ** Changed in: chromium-browser (Ubuntu) Assignee: (unassigned) => Olivier Tilloy (osomon) ** Changed in: chromium-browser (Ubuntu) Importance: Undecided => Low ** Changed in: chromium-browser (Ubuntu) Status: New => Triaged -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/1771847 Title: chromium-browser.svg icon is outdated Status in chromium-browser package in Ubuntu: In Progress Bug description: The chromium-browser package installs an SVG icon (/usr/share/icons/hicolor/scalable/apps/chromium-browser.svg) - that file comes from the debian/ directory, not from the upstream tarballs, and as such is outdated in comparison with the PNG icons at various sizes that come from the tarballs. I wasn't able to find a recent version of the chromium icon in SVG form, so that icon should be removed. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1771847/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1771847] Re: chromium-browser.svg icon is outdated
Fixed in the snap: https://git.launchpad.net/~chromium-team/chromium- browser/+git/snappy- packaging/commit/?id=a01fabc65e9ecdca3382d114f7b526f04ffd81bc ** Changed in: chromium-browser (Ubuntu) Status: Triaged => In Progress -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/1771847 Title: chromium-browser.svg icon is outdated Status in chromium-browser package in Ubuntu: In Progress Bug description: The chromium-browser package installs an SVG icon (/usr/share/icons/hicolor/scalable/apps/chromium-browser.svg) - that file comes from the debian/ directory, not from the upstream tarballs, and as such is outdated in comparison with the PNG icons at various sizes that come from the tarballs. I wasn't able to find a recent version of the chromium icon in SVG form, so that icon should be removed. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1771847/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1771847] Re: chromium-browser.svg icon is outdated
And I updated the icon in the snap store, too. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/1771847 Title: chromium-browser.svg icon is outdated Status in chromium-browser package in Ubuntu: In Progress Bug description: The chromium-browser package installs an SVG icon (/usr/share/icons/hicolor/scalable/apps/chromium-browser.svg) - that file comes from the debian/ directory, not from the upstream tarballs, and as such is outdated in comparison with the PNG icons at various sizes that come from the tarballs. I wasn't able to find a recent version of the chromium icon in SVG form, so that icon should be removed. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1771847/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1761593] Re: Uninstall left nouveau blacklisted
This bug was fixed in the package nvidia-graphics-drivers-340 - 340.106-0ubuntu5 --- nvidia-graphics-drivers-340 (340.106-0ubuntu5) cosmic; urgency=medium * debian/nvidia-340.maintscript, debian/templates/nvidia-graphics-drivers.maintscript.in, debian/templates/nvidia-graphics-drivers.postinst.in: - Remove the blacklist file manually, since dpkg-maintscript-helper won't work in this case. Fixes FTBFS. -- Alberto Milone Wed, 16 May 2018 19:30:39 +0200 ** Changed in: nvidia-graphics-drivers-340 (Ubuntu) Status: Triaged => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-graphics-drivers-340 in Ubuntu. https://bugs.launchpad.net/bugs/1761593 Title: Uninstall left nouveau blacklisted Status in nvidia-graphics-drivers-340 package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-390 package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-340 source package in Bionic: New Status in nvidia-graphics-drivers-390 source package in Bionic: Triaged Bug description: Following a successful install and subsequent use of nvidia-340 - uninstallation of nvidia via Additional Drivers led to a reboot to a desktop at 640x480 px. Investigation found an nvidia created file left on the system blacklisting nouveau, deleted file and rebooted to normal desktop. Didn't think about ubuntu-reporting this - can try and replicate and apport-collect if it's of any use. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-340/+bug/1761593/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1771847] Re: chromium-browser.svg icon is outdated
** Branch linked: lp:~chromium-team/chromium-browser/cosmic-dev ** Branch linked: lp:~chromium-team/chromium-browser/bionic-dev ** Branch linked: lp:~chromium-team/chromium-browser/artful-dev ** Branch linked: lp:~chromium-team/chromium-browser/xenial-dev ** Branch linked: lp:~chromium-team/chromium-browser/cosmic-beta ** Branch linked: lp:~chromium-team/chromium-browser/bionic-beta ** Branch linked: lp:~chromium-team/chromium-browser/artful-beta ** Branch linked: lp:~chromium-team/chromium-browser/xenial-beta ** Branch linked: lp:~chromium-team/chromium-browser/cosmic-stable ** Branch linked: lp:~chromium-team/chromium-browser/bionic-stable ** Branch linked: lp:~chromium-team/chromium-browser/artful-stable ** Branch linked: lp:~chromium-team/chromium-browser/xenial-stable -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/1771847 Title: chromium-browser.svg icon is outdated Status in chromium-browser package in Ubuntu: Fix Committed Bug description: The chromium-browser package installs an SVG icon (/usr/share/icons/hicolor/scalable/apps/chromium-browser.svg) - that file comes from the debian/ directory, not from the upstream tarballs, and as such is outdated in comparison with the PNG icons at various sizes that come from the tarballs. I wasn't able to find a recent version of the chromium icon in SVG form, so that icon should be removed. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1771847/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1771847] Re: chromium-browser.svg icon is outdated
** Changed in: chromium-browser (Ubuntu) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/1771847 Title: chromium-browser.svg icon is outdated Status in chromium-browser package in Ubuntu: Fix Committed Bug description: The chromium-browser package installs an SVG icon (/usr/share/icons/hicolor/scalable/apps/chromium-browser.svg) - that file comes from the debian/ directory, not from the upstream tarballs, and as such is outdated in comparison with the PNG icons at various sizes that come from the tarballs. I wasn't able to find a recent version of the chromium icon in SVG form, so that icon should be removed. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1771847/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1771847] Re: chromium-browser.svg icon is outdated
And for completeness I also updated the branding of: - https://launchpad.net/~chromium-team - https://launchpad.net/chromium-project - https://launchpad.net/chromium-browser - https://launchpad.net/chromium-v8 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/1771847 Title: chromium-browser.svg icon is outdated Status in chromium-browser package in Ubuntu: Fix Committed Bug description: The chromium-browser package installs an SVG icon (/usr/share/icons/hicolor/scalable/apps/chromium-browser.svg) - that file comes from the debian/ directory, not from the upstream tarballs, and as such is outdated in comparison with the PNG icons at various sizes that come from the tarballs. I wasn't able to find a recent version of the chromium icon in SVG form, so that icon should be removed. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1771847/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1766137] Re: [regression] Password accepted but login fails (blank purple screen and mouse pointer only)
This bug was fixed in the package gdm3 - 3.28.0-0ubuntu2 --- gdm3 (3.28.0-0ubuntu2) cosmic; urgency=medium * debian/patches/0001-libgdm-Don-t-unref-a-connection-that-s-in-use.patch, debian/patches/0002-libgdm-add-weak-pointer-for-connection-object.patch: Cherry-pick two patches from the 3.28 branch. These fix a refcounting bug in the GDM Client object, which had meant that the DBus connection was being disposed too early in some cases, particularly when logging in after a failed attempt. The symptom of that was that the system hung on a "blank" screen. (LP: #1766137) -- Iain Lane Thu, 17 May 2018 11:56:14 +0100 ** Changed in: gdm3 (Ubuntu) Status: In Progress => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1766137 Title: [regression] Password accepted but login fails (blank purple screen and mouse pointer only) Status in gdm: Fix Released Status in Release Notes for Ubuntu: Fix Released Status in gdm3 package in Ubuntu: Fix Released Status in gnome-shell package in Ubuntu: Invalid Status in gdm3 source package in Bionic: In Progress Status in gnome-shell source package in Bionic: Invalid Bug description: [ Description ] Due to a refcounting bug, a GDBusConnection was getting disposed when it was still required. The symptom of this was that you couldn't log in if you'd got your password wrong. [ Test case ] 1. Boot to GDM 2. Click your username 3. Type the wrong password a couple of times, pressing enter after each time 4. Type the right password If the bug is happening, after 4. the system hangs at a blank screen with the mouse cursor. If you then switch to a VT or otherwise connect to the machine, you can examine the journal and you'll see a G_IS_DBUS_CONNECTION failure. [ Fix ] Marco and I worked upstream on this fix. We found out that there was a problem like this- The GdmClient has a shared GDBusConnection for its operations. The first time someone calls for it, it is created and stored in the object's private structure. Subsequent calls return *a new reference* to this same object. It turned out that the asynchronous method to get the connection was accidentally unreferencing its object before giving it to the caller if it was returning an already-existing connection. For this to work properly, we need to nullify the pointer we stored when the connection goes away, so we know when to make a new one. There were some cases where we didn't add the weak references required to do that. Those are also fixed. [ Regression potential ] Now we share connections more than we did before. We also more carefully track when to clear our object. If we got this wrong, we might end up leaking the connection or dropping it in even more cases. [ Original report ] WORKAROUND: After typing an incorrect password, click Cancel, then click your name, then enter your password again. --- Trying to log into my session (Gnome, Xorg), if I enter the wrong password before entering it correctly, the session doesn't load and I get a purple screen, a mouse cursor, and an invisible but clickable menu in the top right. If I enter it correctly the first time, there is no problem. I've replicated this from a fresh boot, after logging out and after 'sudo service gdm restart' from the Ctrl-Alt-F4 console. This is a fresh install, and didn't occur when I was using a previous install of 18.04 (until Friday). ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gdm3 3.28.0-0ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-15.16-generic 4.15.15 Uname: Linux 4.15.0-15-generic x86_64 ApportVersion: 2.20.9-0ubuntu6 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sun Apr 22 20:31:13 2018 InstallationDate: Installed on 2018-04-22 (0 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180421.1) SourcePackage: gdm3 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/gdm/+bug/1766137/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1737836] Re: Standard clock applet is oversized in Artful
This can happen when you enable “Show weather” in preferences but the weather information failed loading for some reason. Can you try disabling showing the weather? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-panel in Ubuntu. https://bugs.launchpad.net/bugs/1737836 Title: Standard clock applet is oversized in Artful Status in gnome-panel package in Ubuntu: New Bug description: In Artful if the standard clock applet is used there is a dead-space to the left of it. In my first screenshot you can see the dead-space between the indicator-applet and the clock applet. In the second screenshot you can see I've moved the clock applet to the left and the same dead-space exists between it and the inhibit-applet. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: gnome-panel 1:3.24.1-1ubuntu2 ProcVersionSignature: Ubuntu 4.13.0-19.22-generic 4.13.13 Uname: Linux 4.13.0-19-generic x86_64 ApportVersion: 2.20.7-0ubuntu3.6 Architecture: amd64 CurrentDesktop: GNOME-Flashback:GNOME Date: Tue Dec 12 15:19:25 2017 GsettingsChanges: b'org.gnome.gnome-panel.layout' b'object-id-list' b"['window-list', 'workspace-switcher', 'clock', 'indicator-applet', 'inhibit-applet', 'menu-button', 'trash-applet', 'launcher', 'launcher-0', 'launcher-1']" b'org.gnome.gnome-panel.layout' b'toplevel-id-list' b"['bottom-panel']" InstallationDate: Installed on 2017-12-11 (1 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gnome-panel UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-panel/+bug/1737836/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1765261] Re: [regression] Ubuntu 18.04 login screen rejects a valid password on first attempt. Usually works on the second attempt
Second time does not work for me - neither the third, nor the tenth. Once I lock the screen, there is a chance the GNOME environment will reject all password attempts to lock it and I have to lose all my work by forcing a restart. This is a very serious problem. Is there a workaround available? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1765261 Title: [regression] Ubuntu 18.04 login screen rejects a valid password on first attempt. Usually works on the second attempt Status in gnome-shell package in Ubuntu: In Progress Status in gnome-shell source package in Bionic: Confirmed Status in gnome-shell package in Fedora: Fix Released Bug description: Upstream: https://gitlab.gnome.org/GNOME/gnome-shell/issues/240 Ubuntu 18.04 login screen rejects a valid password on first attempt. Always works on the second attempt.. This seems to be a new problem, just started today. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gdm3 3.28.0-0ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-15.16-generic 4.15.15 Uname: Linux 4.15.0-15-generic x86_64 ApportVersion: 2.20.9-0ubuntu5 Architecture: amd64 Date: Thu Apr 19 11:16:17 2018 InstallationDate: Installed on 2017-12-12 (127 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20171211) SourcePackage: gdm3 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1765261/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1737836] Re: Standard clock applet is oversized in Artful
I think I know where is the problem, but I have no time to test / confirm it... If there is no response from me after 1. June then please open upstream bug when all GNOME modules will be migrated to gitlab. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-panel in Ubuntu. https://bugs.launchpad.net/bugs/1737836 Title: Standard clock applet is oversized in Artful Status in gnome-panel package in Ubuntu: New Bug description: In Artful if the standard clock applet is used there is a dead-space to the left of it. In my first screenshot you can see the dead-space between the indicator-applet and the clock applet. In the second screenshot you can see I've moved the clock applet to the left and the same dead-space exists between it and the inhibit-applet. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: gnome-panel 1:3.24.1-1ubuntu2 ProcVersionSignature: Ubuntu 4.13.0-19.22-generic 4.13.13 Uname: Linux 4.13.0-19-generic x86_64 ApportVersion: 2.20.7-0ubuntu3.6 Architecture: amd64 CurrentDesktop: GNOME-Flashback:GNOME Date: Tue Dec 12 15:19:25 2017 GsettingsChanges: b'org.gnome.gnome-panel.layout' b'object-id-list' b"['window-list', 'workspace-switcher', 'clock', 'indicator-applet', 'inhibit-applet', 'menu-button', 'trash-applet', 'launcher', 'launcher-0', 'launcher-1']" b'org.gnome.gnome-panel.layout' b'toplevel-id-list' b"['bottom-panel']" InstallationDate: Installed on 2017-12-11 (1 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gnome-panel UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-panel/+bug/1737836/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1737836] Re: Standard clock applet is oversized in Artful
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: gnome-panel (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-panel in Ubuntu. https://bugs.launchpad.net/bugs/1737836 Title: Standard clock applet is oversized in Artful Status in gnome-panel package in Ubuntu: Confirmed Bug description: In Artful if the standard clock applet is used there is a dead-space to the left of it. In my first screenshot you can see the dead-space between the indicator-applet and the clock applet. In the second screenshot you can see I've moved the clock applet to the left and the same dead-space exists between it and the inhibit-applet. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: gnome-panel 1:3.24.1-1ubuntu2 ProcVersionSignature: Ubuntu 4.13.0-19.22-generic 4.13.13 Uname: Linux 4.13.0-19-generic x86_64 ApportVersion: 2.20.7-0ubuntu3.6 Architecture: amd64 CurrentDesktop: GNOME-Flashback:GNOME Date: Tue Dec 12 15:19:25 2017 GsettingsChanges: b'org.gnome.gnome-panel.layout' b'object-id-list' b"['window-list', 'workspace-switcher', 'clock', 'indicator-applet', 'inhibit-applet', 'menu-button', 'trash-applet', 'launcher', 'launcher-0', 'launcher-1']" b'org.gnome.gnome-panel.layout' b'toplevel-id-list' b"['bottom-panel']" InstallationDate: Installed on 2017-12-11 (1 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gnome-panel UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-panel/+bug/1737836/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1765261] Re: [regression] Ubuntu 18.04 login screen rejects a valid password on first attempt. Usually works on the second attempt
This bug exists in all password prompts throughout the GUI for me: login, VPN, and gpg (running gnome-session under Wayland). Sometimes they work on the first attempt, sometimes it takes 10 tries. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1765261 Title: [regression] Ubuntu 18.04 login screen rejects a valid password on first attempt. Usually works on the second attempt Status in gnome-shell package in Ubuntu: In Progress Status in gnome-shell source package in Bionic: Confirmed Status in gnome-shell package in Fedora: Fix Released Bug description: Upstream: https://gitlab.gnome.org/GNOME/gnome-shell/issues/240 Ubuntu 18.04 login screen rejects a valid password on first attempt. Always works on the second attempt.. This seems to be a new problem, just started today. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gdm3 3.28.0-0ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-15.16-generic 4.15.15 Uname: Linux 4.15.0-15-generic x86_64 ApportVersion: 2.20.9-0ubuntu5 Architecture: amd64 Date: Thu Apr 19 11:16:17 2018 InstallationDate: Installed on 2017-12-12 (127 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20171211) SourcePackage: gdm3 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1765261/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1771812] Re: Software isn't displaying the version of the currently selected snap track
*** This bug is a duplicate of bug 1767445 *** https://bugs.launchpad.net/bugs/1767445 ** This bug has been marked a duplicate of bug 1767445 Uninstalled snaps show most recent channel version, not version to be installed by default -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-software in Ubuntu. https://bugs.launchpad.net/bugs/1771812 Title: Software isn't displaying the version of the currently selected snap track Status in gnome-software package in Ubuntu: New Bug description: https://forum.snapcraft.io/t/gnome-software-plugin-snap-source-for- searches/5392 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-software 3.28.1-0ubuntu4 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 CurrentDesktop: communitheme:ubuntu:GNOME Date: Thu May 17 14:02:32 2018 InstallationDate: Installed on 2017-08-03 (286 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) InstalledPlugins: gnome-software-plugin-flatpak 3.28.1-0ubuntu4 gnome-software-plugin-limba N/A gnome-software-plugin-snap3.28.1-0ubuntu4 SourcePackage: gnome-software UpgradeStatus: Upgraded to bionic on 2018-04-22 (25 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1771812/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1771870] [NEW] [USB-Audio - Logitech G933 Gaming Wireless H, playback] volume controls wrong output
Public bug reported: I have multiple outputs: I have a Dell AC511 USB Soundbar which has its own volume control I have a G15 Logitech Keyboard with volume control I have a G933 Wireless USB Gaming headset with a volume control Currently I have my default output for the whole system is the Dell AC511 USB Soundbar. Chrome has configured communication device as the G933 headset, NOT the "Default" sound. I am unable to control the volume independently of the headset or the system with the correct volume controls. I change volume on my G933 Headset, and the volume of the system is being controlled, and the volume does not change on the headset. I change the volume of the G15 and the Dell AC511, and they correctly control the system volume. This was not an issue on 16.04, each volume control would control its output correctly, while the G15 always controlled the System Volume, never the headset. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu May 17 13:09:51 2018 InstallationDate: Installed on 2018-05-16 (1 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) PackageArchitecture: all ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_Card: G933 Wireless Headset Dongle - Logitech G933 Gaming Wireless H Symptom_PulseAudioLog: Symptom_Type: Volume slider, or mixer problems Title: [USB-Audio - Logitech G933 Gaming Wireless H, playback] volume slider problem UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/21/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1402 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: P8Z77-V LK dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1402:bd03/21/2014:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnP8Z77-VLK:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer ** Affects: alsa-driver (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1771870 Title: [USB-Audio - Logitech G933 Gaming Wireless H, playback] volume controls wrong output Status in alsa-driver package in Ubuntu: New Bug description: I have multiple outputs: I have a Dell AC511 USB Soundbar which has its own volume control I have a G15 Logitech Keyboard with volume control I have a G933 Wireless USB Gaming headset with a volume control Currently I have my default output for the whole system is the Dell AC511 USB Soundbar. Chrome has configured communication device as the G933 headset, NOT the "Default" sound. I am unable to control the volume independently of the headset or the system with the correct volume controls. I change volume on my G933 Headset, and the volume of the system is being controlled, and the volume does not change on the headset. I change the volume of the G15 and the Dell AC511, and they correctly control the system volume. This was not an issue on 16.04, each volume control would control its output correctly, while the G15 always controlled the System Volume, never the headset. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu May 17 13:09:51 2018 InstallationDate: Installed on 2018-05-16 (1 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) PackageArchitecture: all ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_Card: G933 Wireless Headset Dongle - Logitech G933 Gaming Wireless H Symptom_PulseAudioLog: Symptom_Type: Volume slider, or mixer problems Title: [USB-Audio - Logitech G933 Gaming Wireless H, playback] volume slider problem UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/21/2014 dmi.bios.vendor: American Megat
[Desktop-packages] [Bug 1771660] Re: SRU: Make x11-xkb-config M-A: foreign
Hello Matthias, or anyone else affected, Accepted x11-xkb-utils into bionic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/x11-xkb- utils/7.7+3ubuntu0.18.04.1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed.Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested and change the tag from verification-needed-bionic to verification-done-bionic. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-bionic. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance! ** Changed in: x11-xkb-utils (Ubuntu Bionic) Status: New => Fix Committed ** Tags added: verification-needed verification-needed-bionic ** Changed in: x11-xkb-utils (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to x11-xkb-utils in Ubuntu. https://bugs.launchpad.net/bugs/1771660 Title: SRU: Make x11-xkb-config M-A: foreign Status in x11-xkb-utils package in Ubuntu: Fix Released Status in x11-xkb-utils source package in Bionic: Fix Committed Bug description: [Impact] Installing x11-xkb-utils for a foreign architecture is not possible. This is needed to cross build OpenJDK packages. [Test Case] Install build dependencies for openjdk-lts for a foreign architecture. [Regression Potential] None, as afar as I can see. [Acceptance Criteria] The package builds and is installable for foreign architectures. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/x11-xkb-utils/+bug/1771660/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1770971] Re: Update gnome-system-monitor to 3.28.2
Hello Jeremy, or anyone else affected, Accepted gnome-system-monitor into bionic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source /gnome-system-monitor/3.28.2-0ubuntu1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed.Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested and change the tag from verification-needed-bionic to verification-done-bionic. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-bionic. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance! ** Changed in: gnome-system-monitor (Ubuntu Bionic) Status: In Progress => Fix Committed ** Tags added: verification-needed verification-needed-bionic -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-system-monitor in Ubuntu. https://bugs.launchpad.net/bugs/1770971 Title: Update gnome-system-monitor to 3.28.2 Status in gnome-system-monitor package in Ubuntu: Fix Released Status in gnome-system-monitor source package in Bionic: Fix Committed Bug description: Impact -- 3.28.2 is the latest bugfix release in the stable 3.28 series. https://git.gnome.org/browse/gnome-system-monitor/tree/NEWS https://git.gnome.org/browse/gnome-system-monitor/log Test Case - We can test the bugfix: 1. Ubuntu 18.04 LTS uses the snap version of gnome-system-monitor for new installs. To ensure, we're testing the right version, run sudo apt install gnome-system-monitor 2. Install chromium-browser (apt or snap is fine). 3. Run chromium-browser. 4. Run gnome-system-monitor from the command line (to avoid picking the snap version if you have that installed) 5. In the list select "chromium-browser --type=renderer" 6. Click End Process The end process dialog should display "Are you sure you want to end the selected process "chromium-browser" With 3.28.1, it instead displayed a very large dialog with the entire command line argument between those quotation marks. Feel free to uninstall chromium-browser or gnome-system-monitor afterwards. Regression Potential - The GNOME stack has an SRU Micro-release exception https://wiki.ubuntu.com/StableReleaseUpdates#GNOME This is a very minor change. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-system-monitor/+bug/1770971/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1767445] Re: Uninstalled snaps show most recent channel version, not version to be installed by default
Tested gnome-software 3.28.1-0ubuntu4.18.04.1 with gnome-software- plugin-snap 3.28.1-0ubuntu4.18.04.1. The `blender` snap displays the correct version now (the stable release rather than the latest version), same for `intellij-idea-community`, `mumble`, etc... ** Tags removed: verification-needed-bionic ** Tags added: verification-done-bionic -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-software in Ubuntu. https://bugs.launchpad.net/bugs/1767445 Title: Uninstalled snaps show most recent channel version, not version to be installed by default Status in snapd: New Status in Snap Store: New Status in gnome-software package in Ubuntu: Fix Released Status in gnome-software source package in Xenial: Fix Committed Status in gnome-software source package in Bionic: Fix Committed Status in gnome-software source package in Cosmic: Fix Released Bug description: [Impact] GNOME Software can show incorrect version of snap that will be installed on details page. [Test Case] 1. Open GNOME Software. Ensure blender snap is not installed. 2. Select blender snap (tried 28-04-2018, may change if store versions are changed) Expected result: Version label shows version to be installed (stable channel by default) Observed result: Version label shows most recently uploaded version, i.e. from the edge channel. This is not the version that will be installed when clicking install. [Regression Potential] The logic around choosing which version value to show was changed. Could create other bugs with this data. Orignial text: Ubuntu Software, when showing metadata about a snap package, is most of the time, likely to get information which is misleading, since it shows info from the *most recently* uploaded snap, regardless of which channel the snap was uploaded to. An example of this is to search for blender, and see that the version shows the edge channel - 2.80-4de142e0b7b and not the stable channel - 2.79. After actually installing the application, the correct metadata is shown. See https://forum.snapcraft.io/t/unexpected-revision-information- exposed-in-some-situations/5163 for more details. To manage notifications about this bug go to: https://bugs.launchpad.net/snapd/+bug/1767445/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1769891] [NEW] UnicodeDecodeError: 'ascii' codec can't decode byte 0xe2 in position 37: ordinal not in range(128)
You have been subscribed to a public bug:
Hello
duplicity crash after backup because there is a python error
Step to reproduce.
1. Active developper option in software center
2. install the backup python pyckage
3. Lanch a backup with duplicity command
Result :
Type of backup set:Time: Number of volumes:
Full Tue Feb 20 22:00:34 2018 2284
Incremental Thu Feb 22 03:26:48 2018 1
Incremental Fri Feb 23 23:23:09 201842
Incremental Wed Apr 4 15:54:05 2018 151
Incremental Thu Apr 5 04:27:55 2018 1
Incremental Sat Apr 14 21:51:41 2018 1
-
Also found 0 backup sets not part of any chain,
and 1 incomplete backup set.
These may be deleted by running duplicity with the "cleanup" command.
Registering (mktemp) temporary file
/tmp/duplicity-hFkoYG-tempdir/mktemp-1HIleQ-2
Deleting /tmp/duplicity-hFkoYG-tempdir/mktemp-1HIleQ-2
Forgetting temporary file /tmp/duplicity-hFkoYG-tempdir/mktemp-1HIleQ-2
Processing remote manifest
duplicity-inc.20180405T022755Z.to.20180414T195141Z.manifest (154)
Found manifest volume 1
Found 1 volumes in manifest
Registering (mktemp) temporary file
/tmp/duplicity-hFkoYG-tempdir/mktemp-AW3xfd-3
Backtrace of previous error: Traceback (innermost last):
File "/usr/lib/python2.7/dist-packages/duplicity/backend.py", line 369, in
inner_retry
return fn(self, *args)
File "/usr/lib/python2.7/dist-packages/duplicity/backend.py", line 556, in get
"from backend") % util.ufn(local_path.name))
BackendException: File /tmp/duplicity-hFkoYG-tempdir/mktemp-AW3xfd-3 not found
locally after get from backend
Attempt 1 failed. BackendException: File
/tmp/duplicity-hFkoYG-tempdir/mktemp-AW3xfd-3 not found locally after get from
backend
Backtrace of previous error: Traceback (innermost last):
File "/usr/lib/python2.7/dist-packages/duplicity/backend.py", line 369, in
inner_retry
return fn(self, *args)
File "/usr/lib/python2.7/dist-packages/duplicity/backend.py", line 552, in get
self.backend._get(remote_filename, local_path)
File "/usr/lib/python2.7/dist-packages/duplicity/backends/giobackend.py",
line 151, in _get
self.__copy_file(source_file, target_file)
File "/usr/lib/python2.7/dist-packages/duplicity/backends/giobackend.py",
line 124, in __copy_file
None, self.__copy_progress, None)
Error: g-io-error-quark: Error opening file
â/tmp/duplicity-hFkoYG-tempdir/mktemp-AW3xfd-3â: No such file or directory
(1)
Releasing lockfile
/home/username/.cache/deja-dup/078943ce1c0e98d4e44486ca87a6cdd8/lockfile
Removing still remembered temporary file
/tmp/duplicity-hFkoYG-tempdir/mkstemp-useaK1-1
Removing still remembered temporary file
/tmp/duplicity-hFkoYG-tempdir/mktemp-AW3xfd-3
Cleanup of temporary directory /tmp/duplicity-hFkoYG-tempdir failed - this is
probably a bug.
Releasing lockfile
/home/username/.cache/deja-dup/078943ce1c0e98d4e44486ca87a6cdd8/lockfile
Traceback (innermost last):
File "/usr/bin/duplicity", line 1555, in
with_tempdir(main)
File "/usr/bin/duplicity", line 1541, in with_tempdir
fn()
File "/usr/bin/duplicity", line 1393, in main
do_backup(action)
File "/usr/bin/duplicity", line 1523, in do_backup
incremental_backup(sig_chain)
File "/usr/bin/duplicity", line 658, in incremental_backup
sig_chain.get_fileobjs())
File "/usr/lib/python2.7/dist-packages/duplicity/collections.py", line 539,
in get_fileobjs
return [filename_to_fileobj(f) for f in self.get_filenames(time)]
File "/usr/lib/python2.7/dist-packages/duplicity/backend.py", line 676, in
get_fileobj_read
self.get(filename, tdp)
File "/usr/lib/python2.7/dist-packages/duplicity/backend.py", line 392, in
inner_retry
util.uexc(e)), code=code, extra=extra)
File "/usr/lib/python2.7/dist-packages/duplicity/util.py", line 79, in uexc
return ufn(unicode(e).encode('utf-8'))
UnicodeDecodeError: 'ascii' codec can't decode byte 0xe2 in position 37:
ordinal not in range(128)
Releasing lockfile /home/username/.cache/deja-
dup/078943ce1c0e98d4e44486ca87a6cdd8/lockfile
Note : this bug affect eclim and other python pyckages
http://eclim.org
Could you help me please to fix this issus
Best regards
Battant
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: python2.7 2.7.15~rc1-1
ProcVersionSignature: Ubuntu 4.15.0-21.22-generic 4.15.17
Uname: Linux 4.15.0-21-generic x86_64
ApportVersion: 2.20.9-0ubuntu7
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Tue May 8 14:11:35 2018
InstallationDate: Installed on 2018-04-29 (8 days ago)
InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
SourcePackage: python2.7
UpgradeStatus: No upgrade log present (probably fresh install)
** Affects: deja-dup
Importance: Undecided
Status: Confirmed
** Affects: dupl
[Desktop-packages] [Bug 1769891] Re: UnicodeDecodeError: 'ascii' codec can't decode byte 0xe2 in position 37: ordinal not in range(128)
** Package changed: python2.7 (Ubuntu) => duplicity (Ubuntu)
** Package changed: duplicity (Ubuntu) => deja-dup (Ubuntu)
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to duplicity in Ubuntu.
https://bugs.launchpad.net/bugs/1769891
Title:
UnicodeDecodeError: 'ascii' codec can't decode byte 0xe2 in position
37: ordinal not in range(128)
Status in Déjà Dup:
Confirmed
Status in deja-dup package in Ubuntu:
Confirmed
Bug description:
Hello
duplicity crash after backup because there is a python error
Step to reproduce.
1. Active developper option in software center
2. install the backup python pyckage
3. Lanch a backup with duplicity command
Result :
Type of backup set:Time: Number of volumes:
Full Tue Feb 20 22:00:34 2018 2284
Incremental Thu Feb 22 03:26:48 2018 1
Incremental Fri Feb 23 23:23:09 201842
Incremental Wed Apr 4 15:54:05 2018 151
Incremental Thu Apr 5 04:27:55 2018 1
Incremental Sat Apr 14 21:51:41 2018 1
-
Also found 0 backup sets not part of any chain,
and 1 incomplete backup set.
These may be deleted by running duplicity with the "cleanup" command.
Registering (mktemp) temporary file
/tmp/duplicity-hFkoYG-tempdir/mktemp-1HIleQ-2
Deleting /tmp/duplicity-hFkoYG-tempdir/mktemp-1HIleQ-2
Forgetting temporary file /tmp/duplicity-hFkoYG-tempdir/mktemp-1HIleQ-2
Processing remote manifest
duplicity-inc.20180405T022755Z.to.20180414T195141Z.manifest (154)
Found manifest volume 1
Found 1 volumes in manifest
Registering (mktemp) temporary file
/tmp/duplicity-hFkoYG-tempdir/mktemp-AW3xfd-3
Backtrace of previous error: Traceback (innermost last):
File "/usr/lib/python2.7/dist-packages/duplicity/backend.py", line 369, in
inner_retry
return fn(self, *args)
File "/usr/lib/python2.7/dist-packages/duplicity/backend.py", line 556, in
get
"from backend") % util.ufn(local_path.name))
BackendException: File /tmp/duplicity-hFkoYG-tempdir/mktemp-AW3xfd-3 not
found locally after get from backend
Attempt 1 failed. BackendException: File
/tmp/duplicity-hFkoYG-tempdir/mktemp-AW3xfd-3 not found locally after get from
backend
Backtrace of previous error: Traceback (innermost last):
File "/usr/lib/python2.7/dist-packages/duplicity/backend.py", line 369, in
inner_retry
return fn(self, *args)
File "/usr/lib/python2.7/dist-packages/duplicity/backend.py", line 552, in
get
self.backend._get(remote_filename, local_path)
File "/usr/lib/python2.7/dist-packages/duplicity/backends/giobackend.py",
line 151, in _get
self.__copy_file(source_file, target_file)
File "/usr/lib/python2.7/dist-packages/duplicity/backends/giobackend.py",
line 124, in __copy_file
None, self.__copy_progress, None)
Error: g-io-error-quark: Error opening file
â/tmp/duplicity-hFkoYG-tempdir/mktemp-AW3xfd-3â: No such file or directory
(1)
Releasing lockfile
/home/username/.cache/deja-dup/078943ce1c0e98d4e44486ca87a6cdd8/lockfile
Removing still remembered temporary file
/tmp/duplicity-hFkoYG-tempdir/mkstemp-useaK1-1
Removing still remembered temporary file
/tmp/duplicity-hFkoYG-tempdir/mktemp-AW3xfd-3
Cleanup of temporary directory /tmp/duplicity-hFkoYG-tempdir failed - this is
probably a bug.
Releasing lockfile
/home/username/.cache/deja-dup/078943ce1c0e98d4e44486ca87a6cdd8/lockfile
Traceback (innermost last):
File "/usr/bin/duplicity", line 1555, in
with_tempdir(main)
File "/usr/bin/duplicity", line 1541, in with_tempdir
fn()
File "/usr/bin/duplicity", line 1393, in main
do_backup(action)
File "/usr/bin/duplicity", line 1523, in do_backup
incremental_backup(sig_chain)
File "/usr/bin/duplicity", line 658, in incremental_backup
sig_chain.get_fileobjs())
File "/usr/lib/python2.7/dist-packages/duplicity/collections.py", line 539,
in get_fileobjs
return [filename_to_fileobj(f) for f in self.get_filenames(time)]
File "/usr/lib/python2.7/dist-packages/duplicity/backend.py", line 676, in
get_fileobj_read
self.get(filename, tdp)
File "/usr/lib/python2.7/dist-packages/duplicity/backend.py", line 392, in
inner_retry
util.uexc(e)), code=code, extra=extra)
File "/usr/lib/python2.7/dist-packages/duplicity/util.py", line 79, in uexc
return ufn(unicode(e).encode('utf-8'))
UnicodeDecodeError: 'ascii' codec can't decode byte 0xe2 in position 37:
ordinal not in range(128)
Releasing lockfile /home/username/.cache/deja-
dup/078943ce1c0e98d4e44486ca87a6cdd8/lockfile
Note : this bug affect eclim and other python pyckages
http://eclim.org
Could you help me please to fix this issus
Best reg
[Desktop-packages] [Bug 1767873] Re: /usr/lib/gnome-initial-setup/gnome-initial-setup:double free or corruption (!prev)
This bug was fixed in the package gnome-initial-setup - 3.28.0-2ubuntu6.1 --- gnome-initial-setup (3.28.0-2ubuntu6.1) bionic; urgency=medium [ Robert Ancell ] * debian/patches/0001-Add-Ubuntu-mode-with-special-pages.patch: - Fix crash on shutdown in ubuntu-report page (LP: #1767873) [ Spencer Bygraves ] * Update the "What's new" graphic to mention dock and notifications (LP: #1768557) [ Andrea Azzarone ] * Don't autostart if user quits the wizard before completing it (LP: #1768929) [ Jeremy Bicha ] * Drop debian/ubuntu-changes.png to use the version included in 0001-Add-Ubuntu-mode-with-special-pages.patch -- Jeremy Bicha Thu, 03 May 2018 14:06:19 -0400 ** Changed in: gnome-initial-setup (Ubuntu Bionic) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-initial-setup in Ubuntu. https://bugs.launchpad.net/bugs/1767873 Title: /usr/lib/gnome-initial-setup/gnome-initial-setup:double free or corruption (!prev) Status in gnome-initial-setup package in Ubuntu: Fix Released Status in gnome-initial-setup source package in Bionic: Fix Released Bug description: [Impact] gnome-initial-setup might crash when completed, due to a double free. This causes a crash report to show, but the functionality to otherwise work. [Test Case] Check crash reports stop showing on errors.ubuntu.com [Regression Potential] Fix is to use correct GObject API, unlikely to cause further issues. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-initial-setup/+bug/1767873/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1768557] Re: Update what's new graphic for Welcome to Ubuntu wizard
This bug was fixed in the package gnome-initial-setup - 3.28.0-2ubuntu6.1 --- gnome-initial-setup (3.28.0-2ubuntu6.1) bionic; urgency=medium [ Robert Ancell ] * debian/patches/0001-Add-Ubuntu-mode-with-special-pages.patch: - Fix crash on shutdown in ubuntu-report page (LP: #1767873) [ Spencer Bygraves ] * Update the "What's new" graphic to mention dock and notifications (LP: #1768557) [ Andrea Azzarone ] * Don't autostart if user quits the wizard before completing it (LP: #1768929) [ Jeremy Bicha ] * Drop debian/ubuntu-changes.png to use the version included in 0001-Add-Ubuntu-mode-with-special-pages.patch -- Jeremy Bicha Thu, 03 May 2018 14:06:19 -0400 ** Changed in: gnome-initial-setup (Ubuntu Bionic) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-initial-setup in Ubuntu. https://bugs.launchpad.net/bugs/1768557 Title: Update what's new graphic for Welcome to Ubuntu wizard Status in gnome-initial-setup package in Ubuntu: Fix Committed Status in gnome-initial-setup source package in Bionic: Fix Released Bug description: Impact == Ubuntu 18.04 LTS (desktop) features a new Welcome to Ubuntu wizard which shows on the first login after installing or upgrading. This updates the graphic shown on the What's new in Ubuntu screen "Clock and calendar" has been renamed to "Calendar and notifications" "Launcher" has been renamed to "Dock" Test Case = 1. Install the bionic daily build from http://cdimage.ubuntu.com/bionic/daily-live/pending/ (This is needed because that image will include the updated gnome-initial-setup package and represents a preview of 18.04.1. Otherwise, the problem is that the first login after a new install will not have SRUs applied yet and gnome-initial-setup is already running before update-manager will prompt to install updates.) 2. Restart and log in to Ubuntu 3. Verify that the label changes have been made on the first page of the Welcome to Ubuntu wizard Regression Potential None; this is just a substitution of a .png. Other Info == See also https://github.com/CanonicalLtd/desktop-design/issues/101 The graphic is just a .png and is not translatable yet. See LP: #1766277 You can restart the wizard after completing it by removing ~/.config/gnome-initial-setup-done To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-initial-setup/+bug/1768557/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1768929] Re: Ubuntu Welcome wizard shouldn't show at next login if user closes it
This bug was fixed in the package gnome-initial-setup - 3.28.0-2ubuntu6.1 --- gnome-initial-setup (3.28.0-2ubuntu6.1) bionic; urgency=medium [ Robert Ancell ] * debian/patches/0001-Add-Ubuntu-mode-with-special-pages.patch: - Fix crash on shutdown in ubuntu-report page (LP: #1767873) [ Spencer Bygraves ] * Update the "What's new" graphic to mention dock and notifications (LP: #1768557) [ Andrea Azzarone ] * Don't autostart if user quits the wizard before completing it (LP: #1768929) [ Jeremy Bicha ] * Drop debian/ubuntu-changes.png to use the version included in 0001-Add-Ubuntu-mode-with-special-pages.patch -- Jeremy Bicha Thu, 03 May 2018 14:06:19 -0400 ** Changed in: gnome-initial-setup (Ubuntu Bionic) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-initial-setup in Ubuntu. https://bugs.launchpad.net/bugs/1768929 Title: Ubuntu Welcome wizard shouldn't show at next login if user closes it Status in gnome-initial-setup package in Ubuntu: Fix Released Status in gnome-initial-setup source package in Bionic: Fix Released Bug description: Impact -- If a user closes the Welcome to Ubuntu wizard before completing it, it will still automatically start the next time the user logs in. This can be annoying so we're fixing it. Test Case -- 1. Install the bionic daily build from http://cdimage.ubuntu.com/bionic/daily-live/pending/ 2. Restart and log in. 3. The Welcome to Ubuntu wizard appears. Close it by either doing: a. Right Click on the icon in the Dock on the left and select Quit, or b. Click "Welcome to Ubuntu" in the top bar to open the app menu and then select Quit. 4. Log out. 5. Log back in. The Welcome to Ubuntu wizard should not start. Regression Potential Since none of the pages in the Welcome to Ubuntu wizard are mandatory, it is harmless for it to be ignored. Our patch also was careful to not change the "new user" mode which isn't really used in Ubuntu. See LP: #1762287 for details about that mode. Other Info -- We decided to apply this change even in the GNOME session. Ubuntu GNOME 17.04 included gnome-initial-setup by default. GNOME upstream at this time likes the feature where the wizard will show up on next login until it is completed. https://gitlab.gnome.org/Community/Ubuntu/gnome-initial- setup/merge_requests/1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-initial-setup/+bug/1768929/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1728012] Re: Many 3rd party scanner drivers are broken by a sane change
I'd like to add that Epson Perfection V500 works perfectly after installing all official Epson Linux drivers and follow the instructions at number 25: https://bugs.launchpad.net/ubuntu/+source/sane- backends/+bug/1728012/comments/25 But I don't think non-savvy Ubuntu users can figure this out on their own... -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to sane-backends in Ubuntu. https://bugs.launchpad.net/bugs/1728012 Title: Many 3rd party scanner drivers are broken by a sane change Status in sane-backends package in Ubuntu: Confirmed Bug description: Many scanners can no more be used since sane has changed something: The 3rd-party plug-in the vendor provides as .deb package will still install. But the scanner is no more recognized. Scanners that are affected are(besides others): - Epson Perfection V10 - Epson Perfection V1000 - Epson WorkForce GT-1500 - Brother MFC-8510DN - Epson Perfection V33 It is to note that the probability that the scanner manufacturers fix things others broke is below 100%. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: libsane1 1.0.27-1~experimental2ubuntu2 Uname: Linux 4.14.0-041400rc5-lowlatency x86_64 ApportVersion: 2.20.7-0ubuntu3.1 Architecture: amd64 Date: Fri Oct 27 12:35:52 2017 EcryptfsInUse: Yes SourcePackage: sane-backends UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sane-backends/+bug/1728012/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1771876] [NEW] Some apps when clicking on them can lock up the whole system.
Public bug reported: Ubuntu 18.04 First noticed the bug with VirtualBox. When selecting ‘Shared Folders’ and picking a folder it would cause the whole system to freeze and you would have to hard reset. Also effects PCSX2. Not an issue in ubuntu-session. ** Affects: gnome-session (Ubuntu) Importance: Undecided Status: New ** Description changed: + Ubuntu 18.04 + First noticed the bug with VirtualBox. When selecting ‘Shared Folders’ and picking a folder it would cause the whole system to freeze and you would have to hard reset. Also effects PCSX2. Not an issue in ubuntu-session. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-session in Ubuntu. https://bugs.launchpad.net/bugs/1771876 Title: Some apps when clicking on them can lock up the whole system. Status in gnome-session package in Ubuntu: New Bug description: Ubuntu 18.04 First noticed the bug with VirtualBox. When selecting ‘Shared Folders’ and picking a folder it would cause the whole system to freeze and you would have to hard reset. Also effects PCSX2. Not an issue in ubuntu-session. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-session/+bug/1771876/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1768557] Re: Update what's new graphic for Welcome to Ubuntu wizard
** Tags removed: verification-failed-bionic ** Changed in: gnome-initial-setup (Ubuntu Bionic) Status: Fix Released => Triaged -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-initial-setup in Ubuntu. https://bugs.launchpad.net/bugs/1768557 Title: Update what's new graphic for Welcome to Ubuntu wizard Status in gnome-initial-setup package in Ubuntu: Fix Committed Status in gnome-initial-setup source package in Bionic: Triaged Bug description: Impact == Ubuntu 18.04 LTS (desktop) features a new Welcome to Ubuntu wizard which shows on the first login after installing or upgrading. This updates the graphic shown on the What's new in Ubuntu screen "Clock and calendar" has been renamed to "Calendar and notifications" "Launcher" has been renamed to "Dock" Test Case = 1. Install the bionic daily build from http://cdimage.ubuntu.com/bionic/daily-live/pending/ (This is needed because that image will include the updated gnome-initial-setup package and represents a preview of 18.04.1. Otherwise, the problem is that the first login after a new install will not have SRUs applied yet and gnome-initial-setup is already running before update-manager will prompt to install updates.) 2. Restart and log in to Ubuntu 3. Verify that the label changes have been made on the first page of the Welcome to Ubuntu wizard Regression Potential None; this is just a substitution of a .png. Other Info == See also https://github.com/CanonicalLtd/desktop-design/issues/101 The graphic is just a .png and is not translatable yet. See LP: #1766277 You can restart the wizard after completing it by removing ~/.config/gnome-initial-setup-done To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-initial-setup/+bug/1768557/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1771242] Re: Update gnome-desktop3 to 3.28.2
Hello Jeremy, or anyone else affected, Accepted gnome-desktop3 into bionic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/gnome- desktop3/3.28.2-0ubuntu1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed.Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested and change the tag from verification-needed-bionic to verification-done-bionic. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-bionic. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance! ** Changed in: gnome-desktop3 (Ubuntu Bionic) Status: In Progress => Fix Committed ** Tags added: verification-needed verification-needed-bionic -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-desktop3 in Ubuntu. https://bugs.launchpad.net/bugs/1771242 Title: Update gnome-desktop3 to 3.28.2 Status in gnome-desktop3 package in Ubuntu: Fix Released Status in gnome-desktop3 source package in Bionic: Fix Committed Bug description: Impact == This updates the GNOME version number reported in Settings > Details > About to 3.28.2 This is the final scheduled point release for GNOME 3.28. Since we're updating most of the other GNOME packages to 3.28.2, it's appropriate to do this update too. (We might hold this update in -proposed a bit until we update say gnome-shell to 3.28.2) Tne new version also fixes a memory leak and includes some translation fixes. https://git.gnome.org/browse/gnome-desktop/tree/NEWS?h=gnome-3-28 https://git.gnome.org/browse/gnome-desktop/log?h=gnome-3-28 Test Case = From Ubuntu 18.04 LTS, open the Settings app. Navigate to Details > About The GNOME version number should say 3.28.2 Regression Potential There is a micro-release exception for GNOME: https://wiki.ubuntu.com/StableReleaseUpdates#GNOME To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-desktop3/+bug/1771242/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1766137] Re: [regression] Password accepted but login fails (blank purple screen and mouse pointer only)
Hello Chris, or anyone else affected, Accepted gdm3 into bionic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/gdm3/3.28.0-0ubuntu1.1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed.Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested and change the tag from verification-needed-bionic to verification-done-bionic. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-bionic. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance! ** Changed in: gdm3 (Ubuntu Bionic) Status: In Progress => Fix Committed ** Tags added: verification-needed verification-needed-bionic -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1766137 Title: [regression] Password accepted but login fails (blank purple screen and mouse pointer only) Status in gdm: Fix Released Status in Release Notes for Ubuntu: Fix Released Status in gdm3 package in Ubuntu: Fix Released Status in gnome-shell package in Ubuntu: Invalid Status in gdm3 source package in Bionic: Fix Committed Status in gnome-shell source package in Bionic: Invalid Bug description: [ Description ] Due to a refcounting bug, a GDBusConnection was getting disposed when it was still required. The symptom of this was that you couldn't log in if you'd got your password wrong. [ Test case ] 1. Boot to GDM 2. Click your username 3. Type the wrong password a couple of times, pressing enter after each time 4. Type the right password If the bug is happening, after 4. the system hangs at a blank screen with the mouse cursor. If you then switch to a VT or otherwise connect to the machine, you can examine the journal and you'll see a G_IS_DBUS_CONNECTION failure. [ Fix ] Marco and I worked upstream on this fix. We found out that there was a problem like this- The GdmClient has a shared GDBusConnection for its operations. The first time someone calls for it, it is created and stored in the object's private structure. Subsequent calls return *a new reference* to this same object. It turned out that the asynchronous method to get the connection was accidentally unreferencing its object before giving it to the caller if it was returning an already-existing connection. For this to work properly, we need to nullify the pointer we stored when the connection goes away, so we know when to make a new one. There were some cases where we didn't add the weak references required to do that. Those are also fixed. [ Regression potential ] Now we share connections more than we did before. We also more carefully track when to clear our object. If we got this wrong, we might end up leaking the connection or dropping it in even more cases. [ Original report ] WORKAROUND: After typing an incorrect password, click Cancel, then click your name, then enter your password again. --- Trying to log into my session (Gnome, Xorg), if I enter the wrong password before entering it correctly, the session doesn't load and I get a purple screen, a mouse cursor, and an invisible but clickable menu in the top right. If I enter it correctly the first time, there is no problem. I've replicated this from a fresh boot, after logging out and after 'sudo service gdm restart' from the Ctrl-Alt-F4 console. This is a fresh install, and didn't occur when I was using a previous install of 18.04 (until Friday). ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gdm3 3.28.0-0ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-15.16-generic 4.15.15 Uname: Linux 4.15.0-15-generic x86_64 ApportVersion: 2.20.9-0ubuntu6 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sun Apr 22 20:31:13 2018 InstallationDate: Installed on 2018-04-22 (0 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180421.1) SourcePackage: gdm3 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/gdm/+bug/1766137/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1771880] [NEW] Seahorse unable to import certificates in Ubuntu 18.04
Public bug reported: Seahorse 3.20.0-5 / Ubuntu 18.04 LTS / GNOME 3.28.1 When trying to import a certificate into seahorse/gnome-keyring on Ubuntu 18.04, seahorse GUI application shows the 'import' button greyed out, while mouse hovering the "import" button shows the message "Cannot import because there are no compatible importers". This problem doesn't occur on Ubuntu 16.04 LTS (Seahorse 3.18.0), as I've just tested on my wife's laptop, but happens in my Laptop with Ubuntu 18.04 LTS (Seahorse 3.20.0-5). Because that problem, it's not possible to digitally sign documents with LibreOffice. ** Affects: seahorse (Ubuntu) Importance: Undecided Status: New ** Tags: seahorse-3.20.0-5 ubuntu-18.04lts ** Attachment added: "Screenshot from 2018-05-17 15-33-09.png" https://bugs.launchpad.net/bugs/1771880/+attachment/5140999/+files/Screenshot%20from%202018-05-17%2015-33-09.png ** Description changed: Seahorse 3.20.0-5 / Ubuntu 18.04 LTS / GNOME 3.28.1 - - When trying to import a certificate into seahorse/gnome-keyring on Ubuntu 18.04, seahorse GUI application shows the 'import' button is greyed out, while mouse hovering the "import" button shows the message "Cannot import because there are no compatible importers". + When trying to import a certificate into seahorse/gnome-keyring on + Ubuntu 18.04, seahorse GUI application shows the 'import' button greyed + out, while mouse hovering the "import" button shows the message "Cannot + import because there are no compatible importers". This problem doesn't occur on Ubuntu 16.04 LTS (Seahorse 3.18.0), as I've just tested on my wife's laptop, but happens in my Laptop with Ubuntu 18.04 LTS (Seahorse 3.20.0-5). Because that problem, it's not possible to digitally sign documents with LibreOffice. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to seahorse in Ubuntu. https://bugs.launchpad.net/bugs/1771880 Title: Seahorse unable to import certificates in Ubuntu 18.04 Status in seahorse package in Ubuntu: New Bug description: Seahorse 3.20.0-5 / Ubuntu 18.04 LTS / GNOME 3.28.1 When trying to import a certificate into seahorse/gnome-keyring on Ubuntu 18.04, seahorse GUI application shows the 'import' button greyed out, while mouse hovering the "import" button shows the message "Cannot import because there are no compatible importers". This problem doesn't occur on Ubuntu 16.04 LTS (Seahorse 3.18.0), as I've just tested on my wife's laptop, but happens in my Laptop with Ubuntu 18.04 LTS (Seahorse 3.20.0-5). Because that problem, it's not possible to digitally sign documents with LibreOffice. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/seahorse/+bug/1771880/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
Re: [Desktop-packages] [Bug 1767817] Re: Full text search does not work
I have three computers, two desktops and one laptop. Two of them has a newly installed Ubuntu 18.04 and one has an upgraded 18.04 (from 17.10). In one desktop I installed ubuntu 18.04 in virtualbox. For every operating system I installed tracker. Full text search in nautilus doesn't work in any of them. It must be a bug. On máj 8 2018, at 7:05 du, Wolf Walter wrote: > > I have the same problem. Does also not work with the nautilus version > from flathub. > > -- > You received this bug notification because you are subscribed to a > duplicate bug report (1764995). > https://bugs.launchpad.net/bugs/1767817 > > Title: > Full text search does not work > > Status in nautilus package in Ubuntu: > Confirmed > > Bug description: > Background: I have installed Tracker. It has finished indexing. I can > also use Tracker's command line interface to search by content. > > 1. > Description: Ubuntu 18.04 LTS > Release: 18.04 > > 2. > nautilus: > Installed: 1:3.26.3-0ubuntu4 > Candidate: 1:3.26.3-0ubuntu4 > Version table: > *** 1:3.26.3-0ubuntu4 500 > 500 http://fi.archive.ubuntu.com/ubuntu bionic/main amd64 Packages > 100 /var/lib/dpkg/status > > 3. I expect to be able to search files by content from Nautilus, > because this feature worked in 17.10. > > 4. I get no results from full text search unless the search matches > file names. > > To manage notifications about this bug go to: > https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1767817/+subscriptions > -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1767817 Title: Full text search does not work Status in nautilus package in Ubuntu: Confirmed Bug description: Background: I have installed Tracker. It has finished indexing. I can also use Tracker's command line interface to search by content. 1. Description: Ubuntu 18.04 LTS Release: 18.04 2. nautilus: Installed: 1:3.26.3-0ubuntu4 Candidate: 1:3.26.3-0ubuntu4 Version table: *** 1:3.26.3-0ubuntu4 500 500 http://fi.archive.ubuntu.com/ubuntu bionic/main amd64 Packages 100 /var/lib/dpkg/status 3. I expect to be able to search files by content from Nautilus, because this feature worked in 17.10. 4. I get no results from full text search unless the search matches file names. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1767817/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1280300] Re: Desktop contents displayed on resume, before lock screen is shown
I have same issue on Kubuntu 18.04 Is the NSA forcing someone to leave this in on purpose? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-screensaver in Ubuntu. https://bugs.launchpad.net/bugs/1280300 Title: Desktop contents displayed on resume, before lock screen is shown Status in gnome-screensaver package in Ubuntu: Invalid Bug description: I am running 14.04. When I resume from sleep, the contents of my desktop (including any open windows, emails, etc) are displayed onscreen briefly before the unlock screen is shown. This potentially allows an attacker to view the contents of a locked screen. To reproduce: 1) Suspend a machine, e.g. by closing the lid 2) Resume the machine Expected results: Upon resume, the first thing shown onscreen is the screensaver unlock screen. Actual results: Upon resume, the first thing shown onscreen is the set of open windows that were displayed before the machine was put to sleep. After a second or two, the unlock screen is drawn and you have to enter a password to unlock the machine. This is reproducible on my system. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: gnome-screensaver 3.6.1-0ubuntu9 ProcVersionSignature: Ubuntu 3.13.0-8.28-generic 3.13.2 Uname: Linux 3.13.0-8-generic x86_64 ApportVersion: 2.13.2-0ubuntu2 Architecture: amd64 CurrentDesktop: Unity Date: Fri Feb 14 09:05:50 2014 DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-precise-amd64-20130203-1 EcryptfsInUse: Yes GnomeSessionIdleInhibited: No GnomeSessionInhibitors: None GsettingsGnomeSession: org.gnome.desktop.session session-name 'ubuntu' org.gnome.desktop.session idle-delay uint32 300 InstallationDate: Installed on 2013-12-02 (73 days ago) InstallationMedia: Ubuntu 12.04 "Precise" - Build amd64 LIVE Binary 20130203-13:50 SourcePackage: gnome-screensaver UpgradeStatus: Upgraded to trusty on 2014-02-12 (1 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-screensaver/+bug/1280300/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1771660] Re: SRU: Make x11-xkb-config M-A: foreign
** Tags removed: verification-needed verification-needed-bionic ** Tags added: verification-done verification-done-bionic -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to x11-xkb-utils in Ubuntu. https://bugs.launchpad.net/bugs/1771660 Title: SRU: Make x11-xkb-config M-A: foreign Status in x11-xkb-utils package in Ubuntu: Fix Released Status in x11-xkb-utils source package in Bionic: Fix Committed Bug description: [Impact] Installing x11-xkb-utils for a foreign architecture is not possible. This is needed to cross build OpenJDK packages. [Test Case] Install build dependencies for openjdk-lts for a foreign architecture. [Regression Potential] None, as afar as I can see. [Acceptance Criteria] The package builds and is installable for foreign architectures. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/x11-xkb-utils/+bug/1771660/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1767445] Re: Uninstalled snaps show most recent channel version, not version to be installed by default
Hello Adam, or anyone else affected, Accepted gnome-software into xenial-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/gnome- software/3.20.5-0ubuntu0.16.04.11 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed.Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested and change the tag from verification-needed-xenial to verification-done-xenial. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-xenial. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance! ** Tags added: verification-needed-xenial -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-software in Ubuntu. https://bugs.launchpad.net/bugs/1767445 Title: Uninstalled snaps show most recent channel version, not version to be installed by default Status in snapd: New Status in Snap Store: New Status in gnome-software package in Ubuntu: Fix Released Status in gnome-software source package in Xenial: Fix Committed Status in gnome-software source package in Bionic: Fix Committed Status in gnome-software source package in Cosmic: Fix Released Bug description: [Impact] GNOME Software can show incorrect version of snap that will be installed on details page. [Test Case] 1. Open GNOME Software. Ensure blender snap is not installed. 2. Select blender snap (tried 28-04-2018, may change if store versions are changed) Expected result: Version label shows version to be installed (stable channel by default) Observed result: Version label shows most recently uploaded version, i.e. from the edge channel. This is not the version that will be installed when clicking install. [Regression Potential] The logic around choosing which version value to show was changed. Could create other bugs with this data. Orignial text: Ubuntu Software, when showing metadata about a snap package, is most of the time, likely to get information which is misleading, since it shows info from the *most recently* uploaded snap, regardless of which channel the snap was uploaded to. An example of this is to search for blender, and see that the version shows the edge channel - 2.80-4de142e0b7b and not the stable channel - 2.79. After actually installing the application, the correct metadata is shown. See https://forum.snapcraft.io/t/unexpected-revision-information- exposed-in-some-situations/5163 for more details. To manage notifications about this bug go to: https://bugs.launchpad.net/snapd/+bug/1767445/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1763736] Re: Snaps without icons not showing
Hello frenchy82, or anyone else affected, Accepted gnome-software into xenial-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/gnome- software/3.20.5-0ubuntu0.16.04.11 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed.Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested and change the tag from verification-needed-xenial to verification-done-xenial. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-xenial. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance! ** Tags added: verification-needed verification-needed-xenial -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-software in Ubuntu. https://bugs.launchpad.net/bugs/1763736 Title: Snaps without icons not showing Status in gnome-software package in Ubuntu: Fix Released Status in gnome-software source package in Xenial: Fix Committed Status in gnome-software source package in Artful: Won't Fix Status in gnome-software source package in Bionic: Fix Released Bug description: [Impact] Snaps that do not provide icons do not show in GNOME Software. They do show on the snapcraft.io website using a default icon. [Test Case] 1. Open GNOME Software 2. Search for "communitheme" Expected result: Community Theme snap shows, using an appropriate icon. Observed result (2 May 2018): Community Theme snap does not show. Note that if the snap is updated in the store this behaviour will change - so will have to check another snap. [Regression Potential] The fix adds the default icon to snaps that do not have one. This will cause more snaps to show, which could expose new bugs. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1763736/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1768779] Re: Snap channel selection list not scrollable
Hello Michal, or anyone else affected, Accepted gnome-software into xenial-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/gnome- software/3.20.5-0ubuntu0.16.04.11 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed.Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested and change the tag from verification-needed-xenial to verification-done-xenial. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-xenial. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance! ** Tags added: verification-needed-xenial -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-software in Ubuntu. https://bugs.launchpad.net/bugs/1768779 Title: Snap channel selection list not scrollable Status in gnome-software package in Ubuntu: Fix Released Status in gnome-software source package in Xenial: Fix Committed Status in gnome-software source package in Bionic: Fix Committed Status in gnome-software source package in Cosmic: Fix Released Bug description: [Impact] Snaps with many channels/branches (e.g. communitheme) make the channel selector too large - it should use a scrollable window if there are many. [Test Case] 1. Search for ”communitheme” in the store 2. Open ”communitheme” result 3. Click on the channel selection button 4. You will see a popup with loong list of channels 5. Try to scroll to see more entries Expected result: You can scroll the list What happen instead: You cannot scroll the list [Regression Potential] Solution is to use a GtkScrolledWindow for the list. Could cause other UI bugs to occur. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1768779/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
