[Touch-packages] [Bug 1927854] [NEW] Warning when updating to version 0.3.10
Public bug reported: I have updated to usb-creator-kde using aptitude. During the update, this warning is displayed: /usr/lib/python3/dist-packages/usbcreator/frontends/kde/frontend.py:140: SyntaxWarning: "is not" with a literal. Did you mean "!="? if self.__img is not '': (I don't know whether this problem also occurred with earlier versions, i.e., whether is it a regression. I also don't know whether this problem only affects the update or also the installation.) ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: xorg 1:7.7+22ubuntu1 ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12 Uname: Linux 5.11.0-16-generic x86_64 ApportVersion: 2.20.11-0ubuntu65 Architecture: amd64 BootLog: Error: [Errno 13] Keine Berechtigung: '/var/log/boot.log' CasperMD5CheckResult: unknown CompositorRunning: None CurrentDesktop: KDE Date: Sun May 9 12:35:17 2021 DistUpgraded: 2021-05-01 11:12:51,168 DEBUG Running PostInstallScript: './xorg_fix_proprietary.py' DistroCodename: hirsute DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation CoffeeLake-U GT3e [Iris Plus Graphics 655] [8086:3ea5] (rev 01) (prog-if 00 [VGA controller]) Subsystem: Intel Corporation Iris Plus Graphics 655 [8086:2074] InstallationDate: Installed on 2020-03-22 (412 days ago) InstallationMedia: Kubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200322) ProcEnviron: LANGUAGE= PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-16-generic root=UUID=414b307b-775a-488c-a85d-9424fe0dcfda ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to hirsute on 2021-05-01 (8 days ago) dmi.bios.date: 03/09/2020 dmi.bios.release: 5.6 dmi.bios.vendor: Intel Corp. dmi.bios.version: BECFL357.86A.0078.2020.0309.1538 dmi.board.name: NUC8BEB dmi.board.vendor: Intel Corporation dmi.board.version: J72688-306 dmi.chassis.type: 35 dmi.ec.firmware.release: 3.20 dmi.modalias: dmi:bvnIntelCorp.:bvrBECFL357.86A.0078.2020.0309.1538:bd03/09/2020:br5.6:efr3.20:svn:pn:pvr:rvnIntelCorporation:rnNUC8BEB:rvrJ72688-306:cvn:ct35:cvr: version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.104-1build1 version.libgl1-mesa-dri: libgl1-mesa-dri 21.0.1-2 version.libgl1-mesa-glx: libgl1-mesa-glx 21.0.1-2 version.xserver-xorg-core: xserver-xorg-core 2:1.20.11-1ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200714-1ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-1 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug hirsute kubuntu ubuntu wayland-session -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1927854 Title: Warning when updating to version 0.3.10 Status in xorg package in Ubuntu: New Bug description: I have updated to usb-creator-kde using aptitude. During the update, this warning is displayed: /usr/lib/python3/dist-packages/usbcreator/frontends/kde/frontend.py:140: SyntaxWarning: "is not" with a literal. Did you mean "!="? if self.__img is not '': (I don't know whether this problem also occurred with earlier versions, i.e., whether is it a regression. I also don't know whether this problem only affects the update or also the installation.) ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: xorg 1:7.7+22ubuntu1 ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12 Uname: Linux 5.11.0-16-generic x86_64 ApportVersion: 2.20.11-0ubuntu65 Architecture: amd64 BootLog: Error: [Errno 13] Keine Berechtigung: '/var/log/boot.log' CasperMD5CheckResult: unknown CompositorRunning: None CurrentDesktop: KDE Date: Sun May 9 12:35:17 2021 DistUpgraded: 2021-05-01 11:12:51,168 DEBUG Running PostInstallScript: './xorg_fix_proprietary.py' DistroCodename: hirsute DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation CoffeeLake-U GT3e [Iris Plus Graphics 655] [8086:3ea5] (rev 01) (prog-if 00 [VGA controller]) Subsystem: Intel Corporation Iris Plus Graphics 655 [8086:2074] InstallationDate: Installed on 2020-03-22 (412 days ago) InstallationMedia: Kubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200322) ProcEnviron: LANGUAGE= PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-16-generic root=UUID=414b307b-775a-488c-a85d-9424fe0dcfda ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to hirsute on 2021-05-01 (8 days ago) dmi.bios.date: 03/09/2020 dmi.bios.release: 5.6 dmi.bios.vendor: Intel Corp. dmi.bios.version: BECFL357.86A.0078.2020.03
[Touch-packages] [Bug 1826939] Re: Network restart after suspend is unreliable
This problem has not occurred on my machine for some time now. So I think this bug can be closed. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to netbase in Ubuntu. https://bugs.launchpad.net/bugs/1826939 Title: Network restart after suspend is unreliable Status in netbase package in Ubuntu: New Bug description: After suspending my computer to standby and then waking it up again, networking restarts unreliably: Sometimes it restarts fine, sometimes it takes a few seconds to restart, and sometimes it takes more than a minute (I didn't wait longer). When the network wakeup is not finished, pings to my local router get a timeout, and "sudo service networking restart" creates this output: klee@gonzales:~$ ping router PING router (192.168.100.254) 56(84) bytes of data. From gonzales (192.168.100.2) icmp_seq=1 Destination Host Unreachable ^C --- router ping statistics --- 1 packets transmitted, 0 received, +1 errors, 100% packet loss, time 0ms klee@gonzales:~$ sudo service networking status ● networking.service - Raise network interfaces Loaded: loaded (/lib/systemd/system/networking.service; enabled; vendor preset: enabled) Active: active (exited) since Mon 2019-04-29 11:16:05 CEST; 12h ago Docs: man:interfaces(5) Main PID: 1239 (code=exited, status=0/SUCCESS) Tasks: 0 (limit: 4915) Memory: 0B CGroup: /system.slice/networking.service Apr 29 11:15:58 gonzales systemd[1]: Starting Raise network interfaces... Apr 29 11:15:59 gonzales ifup[1239]: ifup: waiting for lock on /run/network/ifstate.eno1 Apr 29 11:16:05 gonzales systemd[1]: Started Raise network interfaces. After I have done a "sudo service networking restart", the output is this: klee@gonzales:~$ sudo service networking status ● networking.service - Raise network interfaces Loaded: loaded (/lib/systemd/system/networking.service; enabled; vendor preset: enabled) Active: active (exited) since Mon 2019-04-29 23:17:00 CEST; 5s ago Docs: man:interfaces(5) Process: 3701 ExecStart=/sbin/ifup -a --read-environment (code=exited, status=0/SUCCESS) Main PID: 3701 (code=exited, status=0/SUCCESS) Tasks: 1 (limit: 4915) Memory: 7.4M CGroup: /system.slice/networking.service └─3728 /sbin/dhclient -1 -4 -v -pf /run/dhclient.eno1.pid -lf /var/lib/dhcp/dhclient.eno1.leases -I -df /var/lib/dhcp/dhclient6.eno1.leases eno1 Apr 29 23:16:59 gonzales ifup[3701]: DHCPDISCOVER on eno1 to 255.255.255.255 port 67 interval 5 (xid=0x53439c24) Apr 29 23:16:59 gonzales dhclient[3728]: DHCPOFFER of 192.168.100.2 from 192.168.100.254 Apr 29 23:16:59 gonzales dhclient[3728]: DHCPREQUEST for 192.168.100.2 on eno1 to 255.255.255.255 port 67 (xid=0x249c4353) Apr 29 23:16:59 gonzales ifup[3701]: DHCPOFFER of 192.168.100.2 from 192.168.100.254 Apr 29 23:16:59 gonzales ifup[3701]: DHCPREQUEST for 192.168.100.2 on eno1 to 255.255.255.255 port 67 (xid=0x249c4353) Apr 29 23:16:59 gonzales dhclient[3728]: DHCPACK of 192.168.100.2 from 192.168.100.254 (xid=0x53439c24) Apr 29 23:16:59 gonzales ifup[3701]: DHCPACK of 192.168.100.2 from 192.168.100.254 (xid=0x53439c24) Apr 29 23:17:00 gonzales dhclient[3728]: bound to 192.168.100.2 -- renewal in 42225 seconds. Apr 29 23:17:00 gonzales ifup[3701]: bound to 192.168.100.2 -- renewal in 42225 seconds. Apr 29 23:17:00 gonzales systemd[1]: Started Raise network interfaces. (And the pings work fine again, too.) This is a regression after the upgrade from 18.10 (where networking wakeup worked fine) to 19.04. Version info: klee@gonzales:~$ lsb_release -rd Description:Ubuntu 19.04 Release:19.04 netbase 5.6 ifupdown 0.8.34ubuntu2 ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: netbase 5.6 ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6 Uname: Linux 5.0.0-13-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 CurrentDesktop: KDE Date: Mon Apr 29 23:19:00 2019 Dependencies: InstallationDate: Installed on 2016-08-06 (996 days ago) InstallationMedia: Kubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) PackageArchitecture: all SourcePackage: netbase UpgradeStatus: Upgraded to disco on 2019-04-21 (8 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/netbase/+bug/1826939/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1676547] Re: No network connectivity after upgrade from 16.04 to 16.10
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1671873 might be a duplicate (or related). -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1676547 Title: No network connectivity after upgrade from 16.04 to 16.10 Status in network-manager package in Ubuntu: In Progress Bug description: nplan was installed during the upgrade process but I had no network connectivity after upgrading. Apparently, no package wanted to manage my ethernet connection. ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: ubuntu-release-upgrader-core 1:16.10.10 ProcVersionSignature: Ubuntu 4.8.0-41.44-generic 4.8.17 Uname: Linux 4.8.0-41-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.3-0ubuntu8.2 Architecture: amd64 CrashDB: ubuntu CurrentDesktop: Unity Date: Mon Mar 27 11:34:04 2017 EcryptfsInUse: Yes InstallationDate: Installed on 2013-01-16 (1531 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Alpha amd64 (20130116) PackageArchitecture: all SourcePackage: ubuntu-release-upgrader Symptom: ubuntu-release-upgrader UpgradeStatus: Upgraded to yakkety on 2017-03-17 (10 days ago) VarLogDistupgradeTermlog: modified.conffile..etc.update-manager.meta-release: [modified] mtime.conffile..etc.update-manager.meta-release: 2013-10-08T06:39:09.818913 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1676547/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1671873] [NEW] Upgrade to Yakkety removes eth0 from /etc/network/interfaces
Public bug reported: I've just upgraded this machine from Kubuntu 16.04 to Kubuntu 16.10 using the uprading UI. Before the upgrade, I had lo and eth0 in /etc/network/interfaces. After the upgrade, there was only lo, no eth0 anymore, leaving me without a network connection. I had to re-enter eth0 into the file and restart the networking service to get networking functionality again. ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: network-manager 1.2.6-0ubuntu1 ProcVersionSignature: Ubuntu 4.8.0-41.44-generic 4.8.17 Uname: Linux 4.8.0-41-generic x86_64 ApportVersion: 2.20.3-0ubuntu8.2 Architecture: amd64 CurrentDesktop: KDE Date: Fri Mar 10 17:24:57 2017 IfupdownConfig: auto lo iface lo inet loopback auto eth0 iface eth0 inet dhcp InstallationDate: Installed on 2012-01-28 (1868 days ago) InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012) IpRoute: default via 192.168.100.254 dev eth0 169.254.0.0/16 dev eth0 scope link metric 1000 192.168.100.0/24 dev eth0 proto kernel scope link src 192.168.100.3 IwConfig: lono wireless extensions. eth0 no wireless extensions. NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true WimaxEnabled=true RfKill: SourcePackage: network-manager UpgradeStatus: Upgraded to yakkety on 2017-03-09 (1 days ago) nmcli-con: NAME UUID TYPE TIMESTAMP TIMESTAMP-REAL AUTOCONNECT AUTOCONNECT-PRIORITY READONLY DBUS-PATH ACTIVE DEVICE STATE ACTIVE-PATH nmcli-dev: DEVICE TYPE STATE DBUS-PATH CONNECTION CON-UUID CON-PATH eth0ethernet unmanaged /org/freedesktop/NetworkManager/Devices/1 -- ---- lo loopback unmanaged /org/freedesktop/NetworkManager/Devices/0 -- ---- nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.2.6connected started none enabled enabled enabled enabled enabled ** Affects: network-manager (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug yakkety -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1671873 Title: Upgrade to Yakkety removes eth0 from /etc/network/interfaces Status in network-manager package in Ubuntu: New Bug description: I've just upgraded this machine from Kubuntu 16.04 to Kubuntu 16.10 using the uprading UI. Before the upgrade, I had lo and eth0 in /etc/network/interfaces. After the upgrade, there was only lo, no eth0 anymore, leaving me without a network connection. I had to re-enter eth0 into the file and restart the networking service to get networking functionality again. ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: network-manager 1.2.6-0ubuntu1 ProcVersionSignature: Ubuntu 4.8.0-41.44-generic 4.8.17 Uname: Linux 4.8.0-41-generic x86_64 ApportVersion: 2.20.3-0ubuntu8.2 Architecture: amd64 CurrentDesktop: KDE Date: Fri Mar 10 17:24:57 2017 IfupdownConfig: auto lo iface lo inet loopback auto eth0 iface eth0 inet dhcp InstallationDate: Installed on 2012-01-28 (1868 days ago) InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012) IpRoute: default via 192.168.100.254 dev eth0 169.254.0.0/16 dev eth0 scope link metric 1000 192.168.100.0/24 dev eth0 proto kernel scope link src 192.168.100.3 IwConfig: lono wireless extensions. eth0 no wireless extensions. NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true WimaxEnabled=true RfKill: SourcePackage: network-manager UpgradeStatus: Upgraded to yakkety on 2017-03-09 (1 days ago) nmcli-con: NAME UUID TYPE TIMESTAMP TIMESTAMP-REAL AUTOCONNECT AUTOCONNECT-PRIORITY READONLY DBUS-PATH ACTIVE DEVICE STATE ACTIVE-PATH nmcli-dev: DEVICE TYPE STATE DBUS-PATH CONNECTION CON-UUID CON-PATH eth0ethernet unmanaged /org/freedesktop/NetworkManager/Devices/1 -- ---- lo loopback unmanaged /org/freedesktop/NetworkManager/Devices/0 -- ---- nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.2.6connected started none enabled enabled enabled enabled enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1671873/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1826939] [NEW] Network restart after suspend is unreliable
Public bug reported: After suspending my computer to standby and then waking it up again, networking restarts unreliably: Sometimes it restarts fine, sometimes it takes a few seconds to restart, and sometimes it takes more than a minute (I didn't wait longer). When the network wakeup is not finished, pings to my local router get a timeout, and "sudo service networking restart" creates this output: klee@gonzales:~$ ping router PING router (192.168.100.254) 56(84) bytes of data. >From gonzales (192.168.100.2) icmp_seq=1 Destination Host Unreachable ^C --- router ping statistics --- 1 packets transmitted, 0 received, +1 errors, 100% packet loss, time 0ms klee@gonzales:~$ sudo service networking status ● networking.service - Raise network interfaces Loaded: loaded (/lib/systemd/system/networking.service; enabled; vendor preset: enabled) Active: active (exited) since Mon 2019-04-29 11:16:05 CEST; 12h ago Docs: man:interfaces(5) Main PID: 1239 (code=exited, status=0/SUCCESS) Tasks: 0 (limit: 4915) Memory: 0B CGroup: /system.slice/networking.service Apr 29 11:15:58 gonzales systemd[1]: Starting Raise network interfaces... Apr 29 11:15:59 gonzales ifup[1239]: ifup: waiting for lock on /run/network/ifstate.eno1 Apr 29 11:16:05 gonzales systemd[1]: Started Raise network interfaces. After I have done a "sudo service networking restart", the output is this: klee@gonzales:~$ sudo service networking status ● networking.service - Raise network interfaces Loaded: loaded (/lib/systemd/system/networking.service; enabled; vendor preset: enabled) Active: active (exited) since Mon 2019-04-29 23:17:00 CEST; 5s ago Docs: man:interfaces(5) Process: 3701 ExecStart=/sbin/ifup -a --read-environment (code=exited, status=0/SUCCESS) Main PID: 3701 (code=exited, status=0/SUCCESS) Tasks: 1 (limit: 4915) Memory: 7.4M CGroup: /system.slice/networking.service └─3728 /sbin/dhclient -1 -4 -v -pf /run/dhclient.eno1.pid -lf /var/lib/dhcp/dhclient.eno1.leases -I -df /var/lib/dhcp/dhclient6.eno1.leases eno1 Apr 29 23:16:59 gonzales ifup[3701]: DHCPDISCOVER on eno1 to 255.255.255.255 port 67 interval 5 (xid=0x53439c24) Apr 29 23:16:59 gonzales dhclient[3728]: DHCPOFFER of 192.168.100.2 from 192.168.100.254 Apr 29 23:16:59 gonzales dhclient[3728]: DHCPREQUEST for 192.168.100.2 on eno1 to 255.255.255.255 port 67 (xid=0x249c4353) Apr 29 23:16:59 gonzales ifup[3701]: DHCPOFFER of 192.168.100.2 from 192.168.100.254 Apr 29 23:16:59 gonzales ifup[3701]: DHCPREQUEST for 192.168.100.2 on eno1 to 255.255.255.255 port 67 (xid=0x249c4353) Apr 29 23:16:59 gonzales dhclient[3728]: DHCPACK of 192.168.100.2 from 192.168.100.254 (xid=0x53439c24) Apr 29 23:16:59 gonzales ifup[3701]: DHCPACK of 192.168.100.2 from 192.168.100.254 (xid=0x53439c24) Apr 29 23:17:00 gonzales dhclient[3728]: bound to 192.168.100.2 -- renewal in 42225 seconds. Apr 29 23:17:00 gonzales ifup[3701]: bound to 192.168.100.2 -- renewal in 42225 seconds. Apr 29 23:17:00 gonzales systemd[1]: Started Raise network interfaces. (And the pings work fine again, too.) This is a regression after the upgrade from 18.10 (where networking wakeup worked fine) to 19.04. Version info: klee@gonzales:~$ lsb_release -rd Description:Ubuntu 19.04 Release:19.04 netbase 5.6 ifupdown 0.8.34ubuntu2 ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: netbase 5.6 ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6 Uname: Linux 5.0.0-13-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 CurrentDesktop: KDE Date: Mon Apr 29 23:19:00 2019 Dependencies: InstallationDate: Installed on 2016-08-06 (996 days ago) InstallationMedia: Kubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) PackageArchitecture: all SourcePackage: netbase UpgradeStatus: Upgraded to disco on 2019-04-21 (8 days ago) ** Affects: netbase (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug disco -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to netbase in Ubuntu. https://bugs.launchpad.net/bugs/1826939 Title: Network restart after suspend is unreliable Status in netbase package in Ubuntu: New Bug description: After suspending my computer to standby and then waking it up again, networking restarts unreliably: Sometimes it restarts fine, sometimes it takes a few seconds to restart, and sometimes it takes more than a minute (I didn't wait longer). When the network wakeup is not finished, pings to my local router get a timeout, and "sudo service networking restart" creates this output: klee@gonzales:~$ ping router PING router (192.168.100.254) 56(84) bytes of data. From gonzales (192.168.100.2) icmp_seq=1 Destination Host Unreachable ^C --- router ping statistics --- 1 packets transmitted, 0 received, +1 errors, 100% packet loss, time 0ms klee@gonza
