[Desktop-packages] [Bug 1987445] [NEW] After upgrade to 22.04 from 20.x execution of the shell fails to start the application
Public bug reported: file: cd maple2020/bin ./xmaple the file has permission to run as a program. Double-click results in nothing. I expected maple to start up. Right click plus "Run as a Program" works. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gjs 1.72.0-3~ubuntu22.04.2 ProcVersionSignature: Ubuntu 5.15.0-46.49-generic 5.15.39 Uname: Linux 5.15.0-46-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Tue Aug 23 23:10:01 2022 ExecutablePath: /usr/bin/gjs-console InstallationDate: Installed on 2021-01-10 (590 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) ProcEnviron: LANG=en_US.UTF-8 LANGUAGE=en_US:en PATH=(custom, user) SHELL=/bin/bash XDG_RUNTIME_DIR= SourcePackage: gjs UpgradeStatus: Upgraded to jammy on 2022-08-17 (6 days ago) ** Affects: gjs (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gjs in Ubuntu. https://bugs.launchpad.net/bugs/1987445 Title: After upgrade to 22.04 from 20.x execution of the shell fails to start the application Status in gjs package in Ubuntu: New Bug description: file: cd maple2020/bin ./xmaple the file has permission to run as a program. Double-click results in nothing. I expected maple to start up. Right click plus "Run as a Program" works. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gjs 1.72.0-3~ubuntu22.04.2 ProcVersionSignature: Ubuntu 5.15.0-46.49-generic 5.15.39 Uname: Linux 5.15.0-46-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Tue Aug 23 23:10:01 2022 ExecutablePath: /usr/bin/gjs-console InstallationDate: Installed on 2021-01-10 (590 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) ProcEnviron: LANG=en_US.UTF-8 LANGUAGE=en_US:en PATH=(custom, user) SHELL=/bin/bash XDG_RUNTIME_DIR= SourcePackage: gjs UpgradeStatus: Upgraded to jammy on 2022-08-17 (6 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gjs/+bug/1987445/+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 1971195] [NEW] gnome-remote-desktop leads to a session crash inside qemu with virtio-vga
Public bug reported: Steps to reproduce: 1. On a jammy host, create a jammy guest: $ qemu-img create -f qcow2 vm.qcow2 50G $ qemu-system-x86_64 -accel kvm -cpu host -smp cpus=4 -m 3072 -device virtio-vga -display gtk,grab-on-hover=on -hda vm.qcow2 -cdrom [jammy ISO] 2. Install Ubuntu in that VM (minimal install), no problems are expected yet. 3. After the installation is concluded and the VM reboots, try to login using the Wayland session (it should be the default, no need to select anything). It will fail and bring you back to the login screen (apparently due to a gnome-shell crash; I don't think the details are relevant to the problem here). What is expected: that both the Wayland and X11 sessions work out-of- the-box. Workaround: remove gnome-remote-desktop, and the Wayland session will work just fine in the conditions described above. This is why I'm reporting this issue in gnome-remote-desktop instead of Wayland or gnome-shell or qemu. I might be wrong though... Extra information: 1. gnome-shell starts as expected if the X11 session is selected instead. 2. Alternatively, using the OpenGL enabled virtio-vga driver also makes it work in both the X11 and Wayland sessions: $ qemu-system-x86_64 -accel kvm -cpu host -smp cpus=4 -m 3072 -device virtio-vga-gl -display gtk,gl=on,grab-on-hover=on -hda vm.qcow2 ** Affects: gnome-remote-desktop (Ubuntu) Importance: Undecided Status: New ** Description changed: Steps to reproduce: 1. Create a jammy guest: $ qemu-img create -f qcow2 vm.qcow2 50G $ qemu-system-x86_64 -accel kvm -cpu host -smp cpus=4 -m 3072 -device virtio-vga -display gtk,grab-on-hover=on -hda vm.qcow2 -cdrom [jammy ISO] 2. Install Ubuntu in that VM (minimal install), no problems are expected yet. 3. After the installation is concluded and the VM reboots, try to login using the Wayland session (it should be the default, no need to select anything). It will fail and bring you back to the login screen (apparently due to a gnome-shell crash; I don't think the details are relevant to the problem here). What is expected: that both the Wayland and X11 sessions work out-of- the-box. Workaround: remove gnome-remote-desktop, and the Wayland session will work just fine in the conditions described above. This is why I'm reporting this issue in gnome-remote-desktop instead of Wayland or - gnome-shell. I might be wrong though... + gnome-shell or qemu. I might be wrong though... Extra information: 1. gnome-shell starts as expected if the X11 session is selected instead. 2. Alternatively, using the OpenGL enabled virtio-vga driver also makes it work in both the X11 and Wayland sessions: $ qemu-system-x86_64 -accel kvm -cpu host -smp cpus=4 -m 3072 -device virtio-vga-gl -display gtk,gl=on,grab-on-hover=on -hda vm.qcow2 ** Description changed: Steps to reproduce: - 1. Create a jammy guest: + 1. On a jammy host, create a jammy guest: $ qemu-img create -f qcow2 vm.qcow2 50G $ qemu-system-x86_64 -accel kvm -cpu host -smp cpus=4 -m 3072 -device virtio-vga -display gtk,grab-on-hover=on -hda vm.qcow2 -cdrom [jammy ISO] 2. Install Ubuntu in that VM (minimal install), no problems are expected yet. 3. After the installation is concluded and the VM reboots, try to login using the Wayland session (it should be the default, no need to select anything). It will fail and bring you back to the login screen (apparently due to a gnome-shell crash; I don't think the details are relevant to the problem here). What is expected: that both the Wayland and X11 sessions work out-of- the-box. Workaround: remove gnome-remote-desktop, and the Wayland session will work just fine in the conditions described above. This is why I'm reporting this issue in gnome-remote-desktop instead of Wayland or gnome-shell or qemu. I might be wrong though... Extra information: 1. gnome-shell starts as expected if the X11 session is selected instead. 2. Alternatively, using the OpenGL enabled virtio-vga driver also makes it work in both the X11 and Wayland sessions: $ qemu-system-x86_64 -accel kvm -cpu host -smp cpus=4 -m 3072 -device virtio-vga-gl -display gtk,gl=on,grab-on-hover=on -hda vm.qcow2 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-remote-desktop in Ubuntu. https://bugs.launchpad.net/bugs/1971195 Title: gnome-remote-desktop leads to a session crash inside qemu with virtio- vga Status in gnome-remote-desktop package in Ubuntu: New Bug description: Steps to reproduce: 1. On a jammy host, create a jammy guest: $ qemu-img create -f qcow2 vm.qcow2 50G $ qemu-system-x86_64 -accel kvm -cpu host -smp cpus=4 -m 3072 -device virtio-vga -display gtk,grab-on-hover=on -hda vm.qcow2 -cdrom [jammy ISO] 2. Install Ubuntu in that VM (minimal install), no problems are expected yet. 3. After the installation is concluded and the VM re
[Desktop-packages] [Bug 1104476] Re: Network manager cannot connect to WPA2/PEAP/MSCHAPv2 enterprise wifi networks without CA_Certificate, like Eduroam
Still happening on Ubuntu 20.04LTS: uname -a Linux nodename 5.15.15-76051515-generic #202201160435~1642693824~20.04~97db1bb~dev-Ubuntu SMP Fri Jan 21 x86_64 x86_64 x86_64 GNU/Linux The workaround suggested in original bug description worked for me but I needed to use someone else's computer in order to find the solution. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager-applet in Ubuntu. https://bugs.launchpad.net/bugs/1104476 Title: Network manager cannot connect to WPA2/PEAP/MSCHAPv2 enterprise wifi networks without CA_Certificate, like Eduroam Status in NetworkManager: Fix Released Status in Release Notes for Ubuntu: Fix Released Status in network-manager-applet package in Ubuntu: Triaged Status in wpasupplicant package in Ubuntu: Triaged Status in network-manager-applet source package in Trusty: Triaged Status in wpasupplicant source package in Trusty: Triaged Status in network-manager package in Debian: New Status in Fedora: Fix Released Status in Gentoo Linux: Fix Released Status in network-manager package in openSUSE: Won't Fix Bug description: HOW TO REPRODUCE: Connect to a MPA2/PEAP/MSCHAPv2 enterprise wifi network that doesn't use a CA Certificate, like Eduroam. RESULT: The computer doesn't connect, as the certificate verification fails. WORKAROUNDS: (http://askubuntu.com/questions/279762/cant-connect-to-wpa2-enterprise-peap) RELEASE NOTES TEXT: When connecting to MPA2/PEAP/MSCHAPv2 enterprise wifi networks that doesn't use a CA Certificate, like Eduroam, the connection fails (http://askubuntu.com/questions/279762/cant-connect-to-wpa2-enterprise-peap) To manage notifications about this bug go to: https://bugs.launchpad.net/network-manager/+bug/1104476/+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 1956365] Re: Firefox snap package can not resolve .local dns names
*** This bug is a duplicate of bug 1838038 *** https://bugs.launchpad.net/bugs/1838038 Not quite the same issue. I have AVAHI/mdns disabled and was using vanilla DNS. It was working OK and recently stopped working. -- 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/1956365 Title: Firefox snap package can not resolve .local dns names Status in firefox package in Ubuntu: Invalid Bug description: Firefox snap package does not resolve .local dns names after recent update. After a recent snap package update of Firefox I can no longer resolve .local DNS names for my local network. This ONLY impacts the Firefox snap package. Brave, Chrome and DNS resolution on the local terminal (ping) are working correctly. When opening https://docker.local developer tools displays the error NS_ERROR_UNKNOWN_HOST gary@orion:~$ ping docker.local PING docker.local (192.168.0.18) 56(84) bytes of data. 64 bytes from docker.local (192.168.0.18): icmp_seq=1 ttl=64 time=2.37 ms 64 bytes from docker.local (192.168.0.18): icmp_seq=2 ttl=64 time=2.74 ms 64 bytes from docker.local (192.168.0.18): icmp_seq=3 ttl=64 time=2.53 ms 64 bytes from docker.local (192.168.0.18): icmp_seq=4 ttl=64 time=2.46 ms 64 bytes from docker.local (192.168.0.18): icmp_seq=5 ttl=64 time=2.41 ms Running WireShark shows Firefox sending a single SOA DNS request to the local DNS server. No DNS requests for the docker.local A record are generated by the Firefox snap package. 563.699461647 192.168.0.101 192.168.0.15DNS 65 Standard query 0x70f9 SOA local 573.702560799 192.168.0.15192.168.0.101 DNS 65 Standard query response 0x70f9 SOA local I have tested this faulty behavior on multiple machines running Ubuntu 20.04 and Ubuntu 21.10. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1956365/+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 1956365] Re: Firefox snap package can not resolve .local dns names
Hello, I think it's something to do with AVAHI resolution within the Firefox snap package. I disabled the AVAHI services on my servers/PCs as it conflicts with .local running on a local DNS server. For some reason .local requests within the Firefox snap package stopped working and just generate the odd SOA .local DNS request. I've now migrated my internal network to .lan and DNS resolution is working correctly. -- 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/1956365 Title: Firefox snap package can not resolve .local dns names Status in firefox package in Ubuntu: Invalid Bug description: Firefox snap package does not resolve .local dns names after recent update. After a recent snap package update of Firefox I can no longer resolve .local DNS names for my local network. This ONLY impacts the Firefox snap package. Brave, Chrome and DNS resolution on the local terminal (ping) are working correctly. When opening https://docker.local developer tools displays the error NS_ERROR_UNKNOWN_HOST gary@orion:~$ ping docker.local PING docker.local (192.168.0.18) 56(84) bytes of data. 64 bytes from docker.local (192.168.0.18): icmp_seq=1 ttl=64 time=2.37 ms 64 bytes from docker.local (192.168.0.18): icmp_seq=2 ttl=64 time=2.74 ms 64 bytes from docker.local (192.168.0.18): icmp_seq=3 ttl=64 time=2.53 ms 64 bytes from docker.local (192.168.0.18): icmp_seq=4 ttl=64 time=2.46 ms 64 bytes from docker.local (192.168.0.18): icmp_seq=5 ttl=64 time=2.41 ms Running WireShark shows Firefox sending a single SOA DNS request to the local DNS server. No DNS requests for the docker.local A record are generated by the Firefox snap package. 563.699461647 192.168.0.101 192.168.0.15DNS 65 Standard query 0x70f9 SOA local 573.702560799 192.168.0.15192.168.0.101 DNS 65 Standard query response 0x70f9 SOA local I have tested this faulty behavior on multiple machines running Ubuntu 20.04 and Ubuntu 21.10. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1956365/+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 1956888] Re: can't manually sort bookmarks anymore
I have this problem. Chromium Version 97.0.4692.71 (Official Build) snap (64-bit) Ubuntu 20.04.3 LTS -- 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/1956888 Title: can't manually sort bookmarks anymore Status in chromium-browser package in Ubuntu: Confirmed Bug description: Ubuntu 21.10 Chromium is installed via snap. chromium97.0.4692.711864 latest/stable Since a few days (weeks ?) I can't anymore drag and drop my bookmarks in the bookmarks view (control + shift + O) nor directly in the bookmarks bar. Bookmarks folders have the same problem. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1956888/+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 1956365] Re: Firefox snap package can not resolve .local dns names
** Changed in: firefox (Ubuntu) Status: New => Invalid -- 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/1956365 Title: Firefox snap package can not resolve .local dns names Status in firefox package in Ubuntu: Invalid Bug description: Firefox snap package does not resolve .local dns names after recent update. After a recent snap package update of Firefox I can no longer resolve .local DNS names for my local network. This ONLY impacts the Firefox snap package. Brave, Chrome and DNS resolution on the local terminal (ping) are working correctly. When opening https://docker.local developer tools displays the error NS_ERROR_UNKNOWN_HOST gary@orion:~$ ping docker.local PING docker.local (192.168.0.18) 56(84) bytes of data. 64 bytes from docker.local (192.168.0.18): icmp_seq=1 ttl=64 time=2.37 ms 64 bytes from docker.local (192.168.0.18): icmp_seq=2 ttl=64 time=2.74 ms 64 bytes from docker.local (192.168.0.18): icmp_seq=3 ttl=64 time=2.53 ms 64 bytes from docker.local (192.168.0.18): icmp_seq=4 ttl=64 time=2.46 ms 64 bytes from docker.local (192.168.0.18): icmp_seq=5 ttl=64 time=2.41 ms Running WireShark shows Firefox sending a single SOA DNS request to the local DNS server. No DNS requests for the docker.local A record are generated by the Firefox snap package. 563.699461647 192.168.0.101 192.168.0.15DNS 65 Standard query 0x70f9 SOA local 573.702560799 192.168.0.15192.168.0.101 DNS 65 Standard query response 0x70f9 SOA local I have tested this faulty behavior on multiple machines running Ubuntu 20.04 and Ubuntu 21.10. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1956365/+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 1956365] Re: Firefox snap package can not resolve .local dns names
Firefox running on Windows 10 is working correctly (latest version). -- 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/1956365 Title: Firefox snap package can not resolve .local dns names Status in firefox package in Ubuntu: New Bug description: Firefox snap package does not resolve .local dns names after recent update. After a recent snap package update of Firefox I can no longer resolve .local DNS names for my local network. This ONLY impacts the Firefox snap package. Brave, Chrome and DNS resolution on the local terminal (ping) are working correctly. When opening https://docker.local developer tools displays the error NS_ERROR_UNKNOWN_HOST gary@orion:~$ ping docker.local PING docker.local (192.168.0.18) 56(84) bytes of data. 64 bytes from docker.local (192.168.0.18): icmp_seq=1 ttl=64 time=2.37 ms 64 bytes from docker.local (192.168.0.18): icmp_seq=2 ttl=64 time=2.74 ms 64 bytes from docker.local (192.168.0.18): icmp_seq=3 ttl=64 time=2.53 ms 64 bytes from docker.local (192.168.0.18): icmp_seq=4 ttl=64 time=2.46 ms 64 bytes from docker.local (192.168.0.18): icmp_seq=5 ttl=64 time=2.41 ms Running WireShark shows Firefox sending a single SOA DNS request to the local DNS server. No DNS requests for the docker.local A record are generated by the Firefox snap package. 563.699461647 192.168.0.101 192.168.0.15DNS 65 Standard query 0x70f9 SOA local 573.702560799 192.168.0.15192.168.0.101 DNS 65 Standard query response 0x70f9 SOA local I have tested this faulty behavior on multiple machines running Ubuntu 20.04 and Ubuntu 21.10. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1956365/+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 1956365] [NEW] Firefox snap package can not resolve .local dns names
Public bug reported: Firefox snap package does not resolve .local dns names after recent update. After a recent snap package update of Firefox I can no longer resolve .local DNS names for my local network. This ONLY impacts the Firefox snap package. Brave, Chrome and DNS resolution on the local terminal (ping) are working correctly. When opening https://docker.local developer tools displays the error NS_ERROR_UNKNOWN_HOST gary@orion:~$ ping docker.local PING docker.local (192.168.0.18) 56(84) bytes of data. 64 bytes from docker.local (192.168.0.18): icmp_seq=1 ttl=64 time=2.37 ms 64 bytes from docker.local (192.168.0.18): icmp_seq=2 ttl=64 time=2.74 ms 64 bytes from docker.local (192.168.0.18): icmp_seq=3 ttl=64 time=2.53 ms 64 bytes from docker.local (192.168.0.18): icmp_seq=4 ttl=64 time=2.46 ms 64 bytes from docker.local (192.168.0.18): icmp_seq=5 ttl=64 time=2.41 ms Running WireShark shows Firefox sending a single SOA DNS request to the local DNS server. No DNS requests for the docker.local A record are generated by the Firefox snap package. 56 3.699461647 192.168.0.101 192.168.0.15DNS 65 Standard query 0x70f9 SOA local 57 3.702560799 192.168.0.15192.168.0.101 DNS 65 Standard query response 0x70f9 SOA local I have tested this faulty behavior on multiple machines running Ubuntu 20.04 and Ubuntu 21.10. ** Affects: firefox (Ubuntu) Importance: Undecided Status: New -- 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/1956365 Title: Firefox snap package can not resolve .local dns names Status in firefox package in Ubuntu: New Bug description: Firefox snap package does not resolve .local dns names after recent update. After a recent snap package update of Firefox I can no longer resolve .local DNS names for my local network. This ONLY impacts the Firefox snap package. Brave, Chrome and DNS resolution on the local terminal (ping) are working correctly. When opening https://docker.local developer tools displays the error NS_ERROR_UNKNOWN_HOST gary@orion:~$ ping docker.local PING docker.local (192.168.0.18) 56(84) bytes of data. 64 bytes from docker.local (192.168.0.18): icmp_seq=1 ttl=64 time=2.37 ms 64 bytes from docker.local (192.168.0.18): icmp_seq=2 ttl=64 time=2.74 ms 64 bytes from docker.local (192.168.0.18): icmp_seq=3 ttl=64 time=2.53 ms 64 bytes from docker.local (192.168.0.18): icmp_seq=4 ttl=64 time=2.46 ms 64 bytes from docker.local (192.168.0.18): icmp_seq=5 ttl=64 time=2.41 ms Running WireShark shows Firefox sending a single SOA DNS request to the local DNS server. No DNS requests for the docker.local A record are generated by the Firefox snap package. 563.699461647 192.168.0.101 192.168.0.15DNS 65 Standard query 0x70f9 SOA local 573.702560799 192.168.0.15192.168.0.101 DNS 65 Standard query response 0x70f9 SOA local I have tested this faulty behavior on multiple machines running Ubuntu 20.04 and Ubuntu 21.10. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1956365/+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 1863390] Re: GPU lockup ring 0 stalled for more than X msec
I think I have the same issue. Ubuntu 20.04. dmesg [350143.716757] radeon :01:05.0: ring 0 stalled for more than 10220msec [350143.716768] radeon :01:05.0: GPU lockup (current fence id 0x09a06e34 last fence id 0x09a06e8e on ring 0) sudo lshw -C display *-display description: VGA compatible controller product: RS780L [Radeon 3000] vendor: Advanced Micro Devices, Inc. [AMD/ATI] physical id: 5 bus info: pci@:01:05.0 version: 00 width: 32 bits clock: 33MHz capabilities: pm msi vga_controller bus_master cap_list rom configuration: driver=radeon latency=0 resources: irq:18 memory:d000-dfff ioport:d000(size=256) memory:fe9f-fe9f memory:fe80-fe8f memory:c-d sudo dpkg -l | grep xserver-xorg-video ii xserver-xorg-video-all 1:7.7+19ubuntu14 amd64X.Org X server -- output driver metapackage ii xserver-xorg-video-amdgpu 19.1.0-1 amd64X.Org X server -- AMDGPU display driver ii xserver-xorg-video-ati 1:19.1.0-1 amd64X.Org X server -- AMD/ATI display driver wrapper ii xserver-xorg-video-fbdev 1:0.5.0-1ubuntu1 amd64X.Org X server -- fbdev display driver ii xserver-xorg-video-intel 2:2.99.917+git20200226-1 amd64X.Org X server -- Intel i8xx, i9xx display driver ii xserver-xorg-video-nouveau 1:1.0.16-1 amd64X.Org X server -- Nouveau display driver ii xserver-xorg-video-nvidia-460 460.91.03-0ubuntu0.20.04.1 amd64NVIDIA binary Xorg driver ii xserver-xorg-video-qxl 0.1.5+git20200331-1amd64X.Org X server -- QXL display driver ii xserver-xorg-video-radeon 1:19.1.0-1 amd64X.Org X server -- AMD/ATI Radeon display driver ii xserver-xorg-video-vesa 1:2.4.0-2 amd64X.Org X server -- VESA display driver ii xserver-xorg-video-vmware 1:13.3.0-3 amd64X.Org X server -- VMware display driver -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-video-ati in Ubuntu. https://bugs.launchpad.net/bugs/1863390 Title: GPU lockup ring 0 stalled for more than X msec Status in xserver-xorg-video-ati package in Ubuntu: Confirmed Bug description: Since the update: xserver-xorg-video-ati-hwe-18.04 (1:19.0.1-1ubuntu1~18.04.1) bionic; which resulted from: https://bugs.launchpad.net/fedora/+source/xserver-xorg-video- ati/+bug/1841718 I've experienced GPU freezes where all video becomes unresponsive, both Xorg and Ctrl+Alt terminal switching, and the GPU fan goes to full. I am still able to access the system via SSH. Sometimes dmesg ends up full of this message repeating over and over: radeon :01:00.0: ring 0 stalled for more than 24040msec radeon :01:00.0: GPU lockup (current fence id 0x9e44 last fence id 0x9e49 on ring 0) I sometimes get a few GPU soft reset which seem to fail in drm(?): radeon :01:00.0: Saved 110839 dwords of commands on ring 0. radeon :01:00.0: GPU softreset: 0x0008 ... radeon :01:00.0: Wait for MC idle timedout ! radeon :01:00.0: Wait for MC idle timedout ! [drm] PCIE GART of 1024M enabled (table at 0x00162000). radeon :01:00.0: WB enabled radeon :01:00.0: fence driver on ring 0 use gpu addr 0x4c00 and cpu addr 0x725651ad radeon :01:00.0: fence driver on ring 3 use gpu addr 0x4c0c and cpu addr 0xc3678ed8 radeon :01:00.0: fence driver on ring 5 use gpu addr 0x00072118 and cpu addr 0xdbd9e01b [drm:r600_ring_test [radeon]] *ERROR* radeon: ring 0 test failed (scratch(0x8504)=0xCAFEDEAD) [drm:evergreen_resume [radeon]] *ERROR* evergreen startup failed on resume Even if the above reset doesn't happen, this freeze always results in a unable to handle page fault" BUG in radeon_ring_backup, entered from various call paths, eg: BUG: unable to handle page fault for address: bc2d80574ffc ... Oops: [#1] SMP PTI CPU: 2 PID: 11243 Comm: kworker/2:1H Not tainted 5.5.0-050500-generic #202001262030 Workqueue: radeon-crtc radeon_flip_work_func [radeon] RIP: 0010:radeon_ring_backup+0xc9/0x140 [ra
[Desktop-packages] [Bug 1924282] [NEW] /etc/hp is empty after installing hplip package - 20.04LTS
Public bug reported: After upgrading to 20.04LTS, my HP-LaserJet 1018 printer stopped printing. Looking at the logs, I found the following errors: E [04/Apr/2021:12:12:55] common/utils.c 177: validate_plugin_version() Plugin version[3.17.10] mismatch with HPLIP version[3.20.3] E [04/Apr/2021:12:12:55] common/utils.c 210: Plugin version is not matching I tried completely purging and re-installing the hplip package and the problem still exists. I then tried installing the correct plugin - here is what happened: * $ sudo apt update Hit:1 http://ca.archive.ubuntu.com/ubuntu focal InRelease Hit:2 http://ca.archive.ubuntu.com/ubuntu focal-updates InRelease Hit:3 http://ca.archive.ubuntu.com/ubuntu focal-backports InRelease Get:4 http://ppa.launchpad.net/system76-dev/stable/ubuntu focal InRelease [17.5 kB] Hit:5 http://security.ubuntu.com/ubuntu focal-security InRelease Fetched 17.5 kB in 1s (22.0 kB/s) Reading package lists... Done Building dependency tree Reading state information... Done All packages are up to date. $ sudo apt install hplip --reinstall Reading package lists... Done Building dependency tree Reading state information... Done 0 upgraded, 0 newly installed, 1 reinstalled, 0 to remove and 0 not upgraded. Need to get 204 kB of archives. After this operation, 0 B of additional disk space will be used. Get:1 http://ca.archive.ubuntu.com/ubuntu focal/main amd64 hplip amd64 3.20.3+dfsg0-2 [204 kB] Fetched 204 kB in 0s (781 kB/s) (Reading database ... 303799 files and directories currently installed.) Preparing to unpack .../hplip_3.20.3+dfsg0-2_amd64.deb ... Unpacking hplip (3.20.3+dfsg0-2) over (3.20.3+dfsg0-2) ... Setting up hplip (3.20.3+dfsg0-2) ... Creating/updating hplip user account... Can't open /etc/hp/hplip.conf: No such file or directory. Can't open /etc/hp/hplip.conf: No such file or directory. Processing triggers for dbus (1.12.16-2ubuntu2.1) ... Processing triggers for man-db (2.9.1-1) ... $ wget https://developers.hp.com/sites/default/files/hplip-3.20.3-plugin.run --2021-04-15 08:51:22-- https://developers.hp.com/sites/default/files/hplip-3.20.3-plugin.run Resolving developers.hp.com (developers.hp.com)... 35.167.236.162, 34.210.182.99 Connecting to developers.hp.com (developers.hp.com)|35.167.236.162|:443... connected. HTTP request sent, awaiting response... 200 OK Length: 11514166 (11M) Saving to: ‘hplip-3.20.3-plugin.run.2’ hplip-3.20.3-plugin 100%[===>] 10.98M 8.32MB/sin 1.3s 2021-04-15 08:51:24 (8.32 MB/s) - ‘hplip-3.20.3-plugin.run.2’ saved [11514166/11514166] $ sh hplip-3.20.3-plugin.run Verifying archive integrity... All good. Uncompressing HPLIP 3.20.3 Plugin Self Extracting Archive.. Error setting home directory: /etc/hp/hplip.conf not found. Is HPLIP installed? $ * I looked in the directory /etc/hp and it was indeed empty! See this question for more info: https://answers.launchpad.net/hplip/+question/696517 ** Affects: hplip (Ubuntu) Importance: Undecided Status: New ** Tags: installation missing-files -- 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/1924282 Title: /etc/hp is empty after installing hplip package - 20.04LTS Status in hplip package in Ubuntu: New Bug description: After upgrading to 20.04LTS, my HP-LaserJet 1018 printer stopped printing. Looking at the logs, I found the following errors: E [04/Apr/2021:12:12:55] common/utils.c 177: validate_plugin_version() Plugin version[3.17.10] mismatch with HPLIP version[3.20.3] E [04/Apr/2021:12:12:55] common/utils.c 210: Plugin version is not matching I tried completely purging and re-installing the hplip package and the problem still exists. I then tried installing the correct plugin - here is what happened: * $ sudo apt update Hit:1 http://ca.archive.ubuntu.com/ubuntu focal InRelease Hit:2 http://ca.archive.ubuntu.com/ubuntu focal-updates InRelease Hit:3 http://ca.archive.ubuntu.com/ubuntu focal-backports InRelease Get:4 http://ppa.launchpad.net/system76-dev/stable/ubuntu focal InRelease [17.5 kB] Hit:5 http://security.ubuntu.com/ubuntu focal-security InRelease Fetched 17.5 kB in 1s (22.0 kB/s) Reading package lists... Done Building dependency tree Reading state information... Done All packages are up to date. $ sudo apt install hplip --reinstall Reading package lists... Done Building dependency tree Reading state information... Done 0 upgraded, 0 newly ins
[Desktop-packages] [Bug 1906600] Re: WiFi disconnects continually (goes "down" in NetworkManager)
I have been running the mainline kernel since Saturday and have not seen any of the network disconnect notifications or password prompts since. I had been seeing several of them a day since the kernel update described in my original comment, so it appears the problem has been fixed for me. -- 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/1906600 Title: WiFi disconnects continually (goes "down" in NetworkManager) Status in Ubuntu MATE: Confirmed Status in linux package in Ubuntu: Incomplete Status in network-manager package in Ubuntu: Confirmed Bug description: Hello everybody and thank you in advance for your help. After a recent update, my machine rebooted and appeared to be fine, but after a short time the WiFi dropped and the NetworkManager applet shows that the interface is down. I am also getting prompted for a password (which was previously saved) and when I click on connect it will establish the connection for a short time, but then goes down again. In some cases this is immediate in others, I will be online for up to approximately 15 minutes before it goes down again. I have tried restarting NetworkManager, but I get the same results (short time up, then down). I tried to review log data, but I am not a linux expert and so I'm not sure that I am looking at the right log, nor do I know exactly what to look for. Here are some lines from around the time of the disconnect and the restarting of NetworkManager: ' Dec 01 21:13:24 bryan-HP-Notebook NetworkManager[22616]: [1606875204.3541] dhcp4 (wlo1): state changed unknown -> bound Dec 01 21:13:24 bryan-HP-Notebook NetworkManager[22616]: [1606875204.3698] device (wlo1): state change: ip-config -> ip-check (reason 'none', sys-iface-state: 'managed') Dec 01 21:13:24 bryan-HP-Notebook NetworkManager[22616]: [1606875204.3772] device (wlo1): state change: ip-check -> secondaries (reason 'none', sys-iface-state: 'managed') Dec 01 21:13:24 bryan-HP-Notebook NetworkManager[22616]: [1606875204.3856] device (wlo1): state change: secondaries -> activated (reason 'none', sys-iface-state: 'managed') Dec 01 21:13:24 bryan-HP-Notebook NetworkManager[22616]: [1606875204.3882] manager: NetworkManager state is now CONNECTED_SITE Dec 01 21:13:24 bryan-HP-Notebook NetworkManager[22616]: [1606875204.3945] device (wlo1): Activation: successful, device activated. Dec 01 21:13:24 bryan-HP-Notebook NetworkManager[22616]: [1606875204.3969] manager: NetworkManager state is now CONNECTED_GLOBAL Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]: [1606875348.8909] device (wlo1): supplicant interface state: completed -> authenticating Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]: [1606875348.8910] device (p2p-dev-wlo1): supplicant management interface state: completed -> authenticating Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]: [1606875348.9011] device (wlo1): supplicant interface state: authenticating -> associating Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]: [1606875348.9012] device (p2p-dev-wlo1): supplicant management interface state: authenticating -> associating Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]: [1606875348.9222] device (wlo1): supplicant interface state: associating -> 4-way handshake Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]: [1606875348.9222] device (p2p-dev-wlo1): supplicant management interface state: associating -> 4-way handshake Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]: [1606875348.9223] sup-iface[0x562ab0adb110,wlo1]: connection disconnected (reason -1) Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]: [1606875348.9297] device (wlo1): supplicant interface state: 4-way handshake -> disconnected Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]: [1606875348.9318] device (wlo1): Activation: (wifi) disconnected during association, asking for new key Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]: [1606875348.9321] device (wlo1): state change: activated -> need-auth (reason 'supplicant-disconnect', sys-iface-state: 'managed') Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]: [1606875348.9526] dhcp4 (wlo1): canceled DHCP transaction Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]: [1606875348.9527] dhcp4 (wlo1): state changed bound -> done Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]: [1606875348.9544] manager: NetworkManager state is now CONNECTING Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]: [1606875348.9603] device (p2p-dev-wlo1): supplicant management interface state: 4-way handshake -> disconnected Dec 01 21:15:49 bryan-HP-Notebook NetworkManager[22616]: [1606875349.4819] device (
[Desktop-packages] [Bug 1906600] Re: WiFi disconnects continually (goes "down" in NetworkManager)
I'm having a similar errors, I think it has something to do with the latest kernel updates. In my case, the kernel modules were updated on Dec 1. From the apt history.log: Start-Date: 2020-12-01 07:41:57 Commandline: aptdaemon role='role-commit-packages' sender=':1.297' Install: linux-image-5.4.0-56-generic:amd64 (5.4.0-56.62, automatic), linux-headers-5.4.0-56-generic:amd64 (5.4.0-56.62, automatic), linux-headers-5.4.0-56:amd64 (5.4.0-56.62, automatic), linux-modules-extra-5.4.0-56-generic:amd64 (5.4.0-56.62, automatic), linux-modules-5.4.0-56-generic:amd64 (5.4.0-56.62, automatic) Upgrade: linux-headers-generic:amd64 (5.4.0.54.57, 5.4.0.56.59), linux-libc-dev:amd64 (5.4.0-54.60, 5.4.0-56.62), linux-image-generic:amd64 (5.4.0.54.57, 5.4.0.56.59), snapd:amd64 (2.47.1+20.04, 2.48+20.04), linux-generic:amd64 (5.4.0.54.57, 5.4.0.56.59) End-Date: 2020-12-01 07:43:16 I didn't restart my computer at the time, but shut it down overnight and restarted in the morning of December 2, and that's when I started having very similar issues as described in the original submission. The biggest difference is that the time period of WiFi network disconnects is longer - normally it'll work for a half hour or more, but eventually I'll get disconnected and prompted for a password on a network that I've been connecting to for years. Might have something to do with Realtek wireless adapters: allan ~ $ lspci | grep -i WiFi 03:00.0 Network controller: Realtek Semiconductor Co., Ltd. RTL8188CE 802.11b/g/n WiFi Adapter (rev 01) -- 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/1906600 Title: WiFi disconnects continually (goes "down" in NetworkManager) Status in Ubuntu MATE: New Status in linux package in Ubuntu: Incomplete Status in network-manager package in Ubuntu: Confirmed Bug description: Hello everybody and thank you in advance for your help. After a recent update, my machine rebooted and appeared to be fine, but after a short time the WiFi dropped and the NetworkManager applet shows that the interface is down. I am also getting prompted for a password (which was previously saved) and when I click on connect it will establish the connection for a short time, but then goes down again. In some cases this is immediate in others, I will be online for up to approximately 15 minutes before it goes down again. I have tried restarting NetworkManager, but I get the same results (short time up, then down). I tried to review log data, but I am not a linux expert and so I'm not sure that I am looking at the right log, nor do I know exactly what to look for. Here are some lines from around the time of the disconnect and the restarting of NetworkManager: ' Dec 01 21:13:24 bryan-HP-Notebook NetworkManager[22616]: [1606875204.3541] dhcp4 (wlo1): state changed unknown -> bound Dec 01 21:13:24 bryan-HP-Notebook NetworkManager[22616]: [1606875204.3698] device (wlo1): state change: ip-config -> ip-check (reason 'none', sys-iface-state: 'managed') Dec 01 21:13:24 bryan-HP-Notebook NetworkManager[22616]: [1606875204.3772] device (wlo1): state change: ip-check -> secondaries (reason 'none', sys-iface-state: 'managed') Dec 01 21:13:24 bryan-HP-Notebook NetworkManager[22616]: [1606875204.3856] device (wlo1): state change: secondaries -> activated (reason 'none', sys-iface-state: 'managed') Dec 01 21:13:24 bryan-HP-Notebook NetworkManager[22616]: [1606875204.3882] manager: NetworkManager state is now CONNECTED_SITE Dec 01 21:13:24 bryan-HP-Notebook NetworkManager[22616]: [1606875204.3945] device (wlo1): Activation: successful, device activated. Dec 01 21:13:24 bryan-HP-Notebook NetworkManager[22616]: [1606875204.3969] manager: NetworkManager state is now CONNECTED_GLOBAL Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]: [1606875348.8909] device (wlo1): supplicant interface state: completed -> authenticating Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]: [1606875348.8910] device (p2p-dev-wlo1): supplicant management interface state: completed -> authenticating Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]: [1606875348.9011] device (wlo1): supplicant interface state: authenticating -> associating Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]: [1606875348.9012] device (p2p-dev-wlo1): supplicant management interface state: authenticating -> associating Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]: [1606875348.9222] device (wlo1): supplicant interface state: associating -> 4-way handshake Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]: [1606
[Desktop-packages] [Bug 1904744] Re: cups-browsed crashes when printing test page to remote printer
** Attachment added: "troubleshoot.txt" https://bugs.launchpad.net/ubuntu/+source/cups-filters/+bug/1904744/+attachment/5435680/+files/troubleshoot.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to cups-filters in Ubuntu. https://bugs.launchpad.net/bugs/1904744 Title: cups-browsed crashes when printing test page to remote printer Status in cups-filters package in Ubuntu: New Bug description: 1) lsb_release -rd Description: Ubuntu 20.04.1 LTS Release: 20.04 2) apt-cache policy cups-filters cups-filters: Installed: 1.27.4-1 Candidate: 1.27.4-1 Version table: *** 1.27.4-1 500 500 http://hk.archive.ubuntu.com/ubuntu focal/main amd64 Packages 100 /var/lib/dpkg/status 3) I have several Ubuntu 20.04 LTS desktops configured to print to a CUPS print server with 4 printers. 3 of the printers work OK, the other one I can print a test page locally, I would expect sending a test page from one of the desktops would result in the test page printing. 4) but sending a test page from one of the desktops results in the client CUPS showing: Paused - "No destination host name supplied by cups-browsed for printer "Grassjewel", is cups-browsed running?" When I check on the desktop system: systemctl status cups-browsed cups-browsed.service - Make remote CUPS printers available locally Loaded: loaded (/lib/systemd/system/cups-browsed.service; enabled; vendor preset: enabled) Active: failed (Result: core-dump) since Wed 2020-11-18 21:31:48 HKT; 23min ago Process: 22293 ExecStart=/usr/sbin/cups-browsed (code=dumped, signal=SEGV) Main PID: 22293 (code=dumped, signal=SEGV) Nov 18 21:31:48 Bobcat systemd[1]: cups-browsed.service: Main process exited, code=dumped, status=11/SEGV Nov 18 21:31:48 Bobcat systemd[1]: cups-browsed.service: Failed with result 'core-dump'. Additional information: The 3 working printers are different manufacturer laser printers, on the network. The problem printer is an Epson dot-matrix printer connected to the CUPS server via a USB/Parallel converter. Log files and core dump attached. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups-filters/+bug/1904744/+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 1904744] Re: cups-browsed crashes when printing test page to remote printer
** Attachment added: "core dump" https://bugs.launchpad.net/ubuntu/+source/cups-filters/+bug/1904744/+attachment/5435681/+files/coredump-cups-browsed_20201118 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to cups-filters in Ubuntu. https://bugs.launchpad.net/bugs/1904744 Title: cups-browsed crashes when printing test page to remote printer Status in cups-filters package in Ubuntu: New Bug description: 1) lsb_release -rd Description: Ubuntu 20.04.1 LTS Release: 20.04 2) apt-cache policy cups-filters cups-filters: Installed: 1.27.4-1 Candidate: 1.27.4-1 Version table: *** 1.27.4-1 500 500 http://hk.archive.ubuntu.com/ubuntu focal/main amd64 Packages 100 /var/lib/dpkg/status 3) I have several Ubuntu 20.04 LTS desktops configured to print to a CUPS print server with 4 printers. 3 of the printers work OK, the other one I can print a test page locally, I would expect sending a test page from one of the desktops would result in the test page printing. 4) but sending a test page from one of the desktops results in the client CUPS showing: Paused - "No destination host name supplied by cups-browsed for printer "Grassjewel", is cups-browsed running?" When I check on the desktop system: systemctl status cups-browsed cups-browsed.service - Make remote CUPS printers available locally Loaded: loaded (/lib/systemd/system/cups-browsed.service; enabled; vendor preset: enabled) Active: failed (Result: core-dump) since Wed 2020-11-18 21:31:48 HKT; 23min ago Process: 22293 ExecStart=/usr/sbin/cups-browsed (code=dumped, signal=SEGV) Main PID: 22293 (code=dumped, signal=SEGV) Nov 18 21:31:48 Bobcat systemd[1]: cups-browsed.service: Main process exited, code=dumped, status=11/SEGV Nov 18 21:31:48 Bobcat systemd[1]: cups-browsed.service: Failed with result 'core-dump'. Additional information: The 3 working printers are different manufacturer laser printers, on the network. The problem printer is an Epson dot-matrix printer connected to the CUPS server via a USB/Parallel converter. Log files and core dump attached. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups-filters/+bug/1904744/+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 1904744] Re: cups-browsed crashes when printing test page to remote printer
** Attachment added: "CUPS error_log" https://bugs.launchpad.net/ubuntu/+source/cups-filters/+bug/1904744/+attachment/5435679/+files/error_log_20201118_2131 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to cups-filters in Ubuntu. https://bugs.launchpad.net/bugs/1904744 Title: cups-browsed crashes when printing test page to remote printer Status in cups-filters package in Ubuntu: New Bug description: 1) lsb_release -rd Description: Ubuntu 20.04.1 LTS Release: 20.04 2) apt-cache policy cups-filters cups-filters: Installed: 1.27.4-1 Candidate: 1.27.4-1 Version table: *** 1.27.4-1 500 500 http://hk.archive.ubuntu.com/ubuntu focal/main amd64 Packages 100 /var/lib/dpkg/status 3) I have several Ubuntu 20.04 LTS desktops configured to print to a CUPS print server with 4 printers. 3 of the printers work OK, the other one I can print a test page locally, I would expect sending a test page from one of the desktops would result in the test page printing. 4) but sending a test page from one of the desktops results in the client CUPS showing: Paused - "No destination host name supplied by cups-browsed for printer "Grassjewel", is cups-browsed running?" When I check on the desktop system: systemctl status cups-browsed cups-browsed.service - Make remote CUPS printers available locally Loaded: loaded (/lib/systemd/system/cups-browsed.service; enabled; vendor preset: enabled) Active: failed (Result: core-dump) since Wed 2020-11-18 21:31:48 HKT; 23min ago Process: 22293 ExecStart=/usr/sbin/cups-browsed (code=dumped, signal=SEGV) Main PID: 22293 (code=dumped, signal=SEGV) Nov 18 21:31:48 Bobcat systemd[1]: cups-browsed.service: Main process exited, code=dumped, status=11/SEGV Nov 18 21:31:48 Bobcat systemd[1]: cups-browsed.service: Failed with result 'core-dump'. Additional information: The 3 working printers are different manufacturer laser printers, on the network. The problem printer is an Epson dot-matrix printer connected to the CUPS server via a USB/Parallel converter. Log files and core dump attached. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups-filters/+bug/1904744/+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 1904744] [NEW] cups-browsed crashes when printing test page to remote printer
Public bug reported: 1) lsb_release -rd Description:Ubuntu 20.04.1 LTS Release:20.04 2) apt-cache policy cups-filters cups-filters: Installed: 1.27.4-1 Candidate: 1.27.4-1 Version table: *** 1.27.4-1 500 500 http://hk.archive.ubuntu.com/ubuntu focal/main amd64 Packages 100 /var/lib/dpkg/status 3) I have several Ubuntu 20.04 LTS desktops configured to print to a CUPS print server with 4 printers. 3 of the printers work OK, the other one I can print a test page locally, I would expect sending a test page from one of the desktops would result in the test page printing. 4) but sending a test page from one of the desktops results in the client CUPS showing: Paused - "No destination host name supplied by cups-browsed for printer "Grassjewel", is cups-browsed running?" When I check on the desktop system: systemctl status cups-browsed cups-browsed.service - Make remote CUPS printers available locally Loaded: loaded (/lib/systemd/system/cups-browsed.service; enabled; vendor preset: enabled) Active: failed (Result: core-dump) since Wed 2020-11-18 21:31:48 HKT; 23min ago Process: 22293 ExecStart=/usr/sbin/cups-browsed (code=dumped, signal=SEGV) Main PID: 22293 (code=dumped, signal=SEGV) Nov 18 21:31:48 Bobcat systemd[1]: cups-browsed.service: Main process exited, code=dumped, status=11/SEGV Nov 18 21:31:48 Bobcat systemd[1]: cups-browsed.service: Failed with result 'core-dump'. Additional information: The 3 working printers are different manufacturer laser printers, on the network. The problem printer is an Epson dot-matrix printer connected to the CUPS server via a USB/Parallel converter. Log files and core dump attached. ** Affects: cups-filters (Ubuntu) Importance: Undecided Status: New ** Attachment added: "cups-browsed log file" https://bugs.launchpad.net/bugs/1904744/+attachment/5435678/+files/cups-browsed_log_20201118_2131 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to cups-filters in Ubuntu. https://bugs.launchpad.net/bugs/1904744 Title: cups-browsed crashes when printing test page to remote printer Status in cups-filters package in Ubuntu: New Bug description: 1) lsb_release -rd Description: Ubuntu 20.04.1 LTS Release: 20.04 2) apt-cache policy cups-filters cups-filters: Installed: 1.27.4-1 Candidate: 1.27.4-1 Version table: *** 1.27.4-1 500 500 http://hk.archive.ubuntu.com/ubuntu focal/main amd64 Packages 100 /var/lib/dpkg/status 3) I have several Ubuntu 20.04 LTS desktops configured to print to a CUPS print server with 4 printers. 3 of the printers work OK, the other one I can print a test page locally, I would expect sending a test page from one of the desktops would result in the test page printing. 4) but sending a test page from one of the desktops results in the client CUPS showing: Paused - "No destination host name supplied by cups-browsed for printer "Grassjewel", is cups-browsed running?" When I check on the desktop system: systemctl status cups-browsed cups-browsed.service - Make remote CUPS printers available locally Loaded: loaded (/lib/systemd/system/cups-browsed.service; enabled; vendor preset: enabled) Active: failed (Result: core-dump) since Wed 2020-11-18 21:31:48 HKT; 23min ago Process: 22293 ExecStart=/usr/sbin/cups-browsed (code=dumped, signal=SEGV) Main PID: 22293 (code=dumped, signal=SEGV) Nov 18 21:31:48 Bobcat systemd[1]: cups-browsed.service: Main process exited, code=dumped, status=11/SEGV Nov 18 21:31:48 Bobcat systemd[1]: cups-browsed.service: Failed with result 'core-dump'. Additional information: The 3 working printers are different manufacturer laser printers, on the network. The problem printer is an Epson dot-matrix printer connected to the CUPS server via a USB/Parallel converter. Log files and core dump attached. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups-filters/+bug/1904744/+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 1902921] Re: Scaling one monitor (to 1.5x in my case) can cause Firefox to lose window features (titlebar, buttons, bookmark bar)
Here's another image with the windows showing in alt-tab mode (whatever that's called - pressed Super button once). ** Attachment added: "Screenshot_2020-11-04_22-54-59.png" https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1902921/+attachment/5431403/+files/Screenshot_2020-11-04_22-54-59.png -- 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/1902921 Title: Scaling one monitor (to 1.5x in my case) can cause Firefox to lose window features (titlebar, buttons, bookmark bar) Status in firefox package in Ubuntu: New Status in xorg-server package in Ubuntu: New Bug description: One monitor is a 4K monitor scaled to 1.5x, the other is a normal 1920x1080 monitor scaled to 1x. While Firefox is already open, after logging in with the lock screen, or modifying display settings, sometimes Firefox will lose the titlebar, address bar, buttons, and bookmark bar. The website being displayed will still show, however not all features are usable (right click menu, mouse icon doesn't change). Reproduction steps: - Change zoom level of one or more monitors to >1.0 but less than 2.0 (have not tested with non-fractional zooms) - Open Firefox and browse to any website - Lock screen or leave computer alone until the screen locks. - Login - Firefox may have lost the window chrome Workaround: - Open Display Settings - Change display settings or zoom level, then change back. Computer info: - Ubuntu 20.04.1 - Fractional Scaling enabled - NVidia GeForce GTX 1080/PCIe/SSE2 - Gnome 3.36.3 - X11 - Samsung LU32J590 4K (3840x2160) @ 1.5x - Dell E2416Hb 1920x1080 rotated portrait left, right of Samsung ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-52.57-generic 5.4.65 Uname: Linux 5.4.0-52-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.gpus..02.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:02:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 435.21 Sun Aug 25 08:17:57 CDT 2019 GCC version: gcc version 9.3.0 (Ubuntu 9.3.0-17ubuntu1~20.04) ApportVersion: 2.20.11-0ubuntu27.10 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Wed Nov 4 09:31:17 2020 DistUpgraded: 2020-04-03 12:51:44,815 DEBUG Running PostInstallScript: './xorg_fix_proprietary.py' DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: NVIDIA Corporation GP104 [GeForce GTX 1080] [10de:1b80] (rev a1) (prog-if 00 [VGA controller]) Subsystem: eVga.com. Corp. GP104 [GeForce GTX 1080] [3842:6188] InstallationDate: Installed on 2018-04-28 (920 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-52-generic root=UUID=dfb5d6fd-4a4e-471d-bb00-77a6729533d8 ro quiet splash pci=nommconf vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to focal on 2020-04-03 (214 days ago) dmi.bios.date: 04/06/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P3.80 dmi.board.name: X99 Extreme4 dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP3.80:bd04/06/2018:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnX99Extreme4:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: To Be Filled By O.E.M. dmi.product.sku: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.8-0ubuntu1~20.04.1 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.4 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version
[Desktop-packages] [Bug 1902921] Re: Scaling one monitor (to 1.5x in my case) can cause Firefox to lose window features (titlebar, buttons, bookmark bar)
@vanvugt Can you describe which parts of Firefox you can't tell are missing? I can update the information if necessary. Regarding which parts are missing here's a list: - titlebar/tabs - minimize, maximize, close buttons - Back/forward/refresh/home buttons, address bar, add-on buttons, settings hamburger menu - Bookmark bar - Scrollbar Navigation with escape button works. Mouse works. Scrolling with mouse works. Initial right-click of the mouse shows the context menu offset from the mouse (showed up on Primary display instead of Secondary where the mouse was clicked). Other right clicks of the mouse show the context menu in the correct place. The dev console shows with all of the buttons and options present. Other applications in windowed or fullscreen mode display on the monitor in the correct resolution and with the window chrome. ** Attachment added: "Screenshot_2020-11-04_22-51-51.png" https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1902921/+attachment/5431401/+files/Screenshot_2020-11-04_22-51-51.png -- 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/1902921 Title: Scaling one monitor (to 1.5x in my case) can cause Firefox to lose window features (titlebar, buttons, bookmark bar) Status in firefox package in Ubuntu: New Status in xorg-server package in Ubuntu: New Bug description: One monitor is a 4K monitor scaled to 1.5x, the other is a normal 1920x1080 monitor scaled to 1x. While Firefox is already open, after logging in with the lock screen, or modifying display settings, sometimes Firefox will lose the titlebar, address bar, buttons, and bookmark bar. The website being displayed will still show, however not all features are usable (right click menu, mouse icon doesn't change). Reproduction steps: - Change zoom level of one or more monitors to >1.0 but less than 2.0 (have not tested with non-fractional zooms) - Open Firefox and browse to any website - Lock screen or leave computer alone until the screen locks. - Login - Firefox may have lost the window chrome Workaround: - Open Display Settings - Change display settings or zoom level, then change back. Computer info: - Ubuntu 20.04.1 - Fractional Scaling enabled - NVidia GeForce GTX 1080/PCIe/SSE2 - Gnome 3.36.3 - X11 - Samsung LU32J590 4K (3840x2160) @ 1.5x - Dell E2416Hb 1920x1080 rotated portrait left, right of Samsung ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-52.57-generic 5.4.65 Uname: Linux 5.4.0-52-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.gpus..02.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:02:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 435.21 Sun Aug 25 08:17:57 CDT 2019 GCC version: gcc version 9.3.0 (Ubuntu 9.3.0-17ubuntu1~20.04) ApportVersion: 2.20.11-0ubuntu27.10 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Wed Nov 4 09:31:17 2020 DistUpgraded: 2020-04-03 12:51:44,815 DEBUG Running PostInstallScript: './xorg_fix_proprietary.py' DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: NVIDIA Corporation GP104 [GeForce GTX 1080] [10de:1b80] (rev a1) (prog-if 00 [VGA controller]) Subsystem: eVga.com. Corp. GP104 [GeForce GTX 1080] [3842:6188] InstallationDate: Installed on 2018-04-28 (920 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-52-generic root=UUID=dfb5d6fd-4a4e-471d-bb00-77a6729533d8 ro quiet splash pci=nommconf vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to focal on 2020-04-03 (214 days ago) dmi.bios.date: 04/06/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P3.80 dmi.board.name: X99 Extreme4 dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP3.80:bd04/06/2018:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnX99Extreme4:rvr:
[Desktop-packages] [Bug 1902921] Re: Scaling one monitor (to 1.5x in my case) can cause Firefox to lose window features (titlebar, buttons, bookmark bar)
** Description changed: One monitor is a 4K monitor scaled to 1.5x, the other is a normal 1920x1080 monitor scaled to 1x. - While Firefox is already open, after logging into the lock screen, + While Firefox is already open, after logging in with the lock screen, sometimes Firefox will lose the titlebar, address bar, buttons, and bookmark bar. The website being displayed will still show, however not all features are usable (right click menu, mouse icon doesn't change). Reproduction steps: - Change zoom level of one or more monitors to >1.0 but less than 2.0 (have not tested with non-fractional zooms) - Open Firefox and browse to any website - Lock screen or leave computer alone until the screen locks. - Login - Firefox may have lost the window chrome Workaround: - Open Display Settings - Change display settings or zoom level, then change back. Computer info: - Ubuntu 20.04.1 - Fractional Scaling enabled - NVidia GeForce GTX 1080/PCIe/SSE2 - Gnome 3.36.3 - X11 - Samsung LU32J590 4K (3840x2160) @ 1.5x - Dell E2416Hb 1920x1080 rotated portrait left, right of Samsung ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-52.57-generic 5.4.65 Uname: Linux 5.4.0-52-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.gpus..02.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:02:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 435.21 Sun Aug 25 08:17:57 CDT 2019 GCC version: gcc version 9.3.0 (Ubuntu 9.3.0-17ubuntu1~20.04) ApportVersion: 2.20.11-0ubuntu27.10 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Wed Nov 4 09:31:17 2020 DistUpgraded: 2020-04-03 12:51:44,815 DEBUG Running PostInstallScript: './xorg_fix_proprietary.py' DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: NVIDIA Corporation GP104 [GeForce GTX 1080] [10de:1b80] (rev a1) (prog-if 00 [VGA controller]) Subsystem: eVga.com. Corp. GP104 [GeForce GTX 1080] [3842:6188] InstallationDate: Installed on 2018-04-28 (920 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-52-generic root=UUID=dfb5d6fd-4a4e-471d-bb00-77a6729533d8 ro quiet splash pci=nommconf vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to focal on 2020-04-03 (214 days ago) dmi.bios.date: 04/06/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P3.80 dmi.board.name: X99 Extreme4 dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP3.80:bd04/06/2018:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnX99Extreme4:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: To Be Filled By O.E.M. dmi.product.sku: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.8-0ubuntu1~20.04.1 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.4 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 ** Description changed: One monitor is a 4K monitor scaled to 1.5x, the other is a normal 1920x1080 monitor scaled to 1x. - While Firefox is already open, after logging in with the lock screen, - sometimes Firefox will lose the titlebar, address bar, buttons, and - bookmark bar. The website being displayed will still show, however not - all features are usable (right click menu, mouse icon doesn't change). + While Firefox is already open, after logging in with the lock scre
[Desktop-packages] [Bug 1902921] Re: Scaling one monitor (to 1.5x in my case) can cause Firefox to lose window features (titlebar, buttons, bookmark bar)
I've attached an image of Netflix showing on the Dell monitor after I changed the zoom level back to 1.5x for the Samsung monitor. The image shows Firefox without the window border. Netflix was not in fullscreen mode. ** Attachment added: "Netflix on Dell monitor without window features, not in fullscreen mode" https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1902921/+attachment/5431155/+files/Screenshot_2020-11-04_09-55-18.png -- 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/1902921 Title: Scaling one monitor (to 1.5x in my case) can cause Firefox to lose window features (titlebar, buttons, bookmark bar) Status in xorg package in Ubuntu: New Bug description: One monitor is a 4K monitor scaled to 1.5x, the other is a normal 1920x1080 monitor scaled to 1x. While Firefox is already open, after logging into the lock screen, sometimes Firefox will lose the titlebar, address bar, buttons, and bookmark bar. The website being displayed will still show, however not all features are usable (right click menu, mouse icon doesn't change). Reproduction steps: - Change zoom level of one or more monitors to >1.0 but less than 2.0 (have not tested with non-fractional zooms) - Open Firefox and browse to any website - Lock screen or leave computer alone until the screen locks. - Login - Firefox may have lost the window chrome Workaround: - Open Display Settings - Change display settings or zoom level, then change back. Computer info: - Ubuntu 20.04.1 - Fractional Scaling enabled - NVidia GeForce GTX 1080/PCIe/SSE2 - Gnome 3.36.3 - X11 - Samsung LU32J590 4K (3840x2160) @ 1.5x - Dell E2416Hb 1920x1080 rotated portrait left, right of Samsung ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-52.57-generic 5.4.65 Uname: Linux 5.4.0-52-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.gpus..02.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:02:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 435.21 Sun Aug 25 08:17:57 CDT 2019 GCC version: gcc version 9.3.0 (Ubuntu 9.3.0-17ubuntu1~20.04) ApportVersion: 2.20.11-0ubuntu27.10 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Wed Nov 4 09:31:17 2020 DistUpgraded: 2020-04-03 12:51:44,815 DEBUG Running PostInstallScript: './xorg_fix_proprietary.py' DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: NVIDIA Corporation GP104 [GeForce GTX 1080] [10de:1b80] (rev a1) (prog-if 00 [VGA controller]) Subsystem: eVga.com. Corp. GP104 [GeForce GTX 1080] [3842:6188] InstallationDate: Installed on 2018-04-28 (920 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-52-generic root=UUID=dfb5d6fd-4a4e-471d-bb00-77a6729533d8 ro quiet splash pci=nommconf vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to focal on 2020-04-03 (214 days ago) dmi.bios.date: 04/06/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P3.80 dmi.board.name: X99 Extreme4 dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP3.80:bd04/06/2018:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnX99Extreme4:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: To Be Filled By O.E.M. dmi.product.sku: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.8-0ubuntu1~20.04.1 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.4 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xse
[Desktop-packages] [Bug 1902921] [NEW] Scaling one monitor (to 1.5x in my case) can cause Firefox to lose window features (titlebar, buttons, bookmark bar)
Public bug reported: One monitor is a 4K monitor scaled to 1.5x, the other is a normal 1920x1080 monitor scaled to 1x. While Firefox is already open, after logging into the lock screen, sometimes Firefox will lose the titlebar, address bar, buttons, and bookmark bar. The website being displayed will still show, however not all features are usable (right click menu, mouse icon doesn't change). Reproduction steps: - Change zoom level of one or more monitors to >1.0 but less than 2.0 (have not tested with non-fractional zooms) - Open Firefox and browse to any website - Lock screen or leave computer alone until the screen locks. - Login - Firefox may have lost the window chrome Workaround: - Open Display Settings - Change display settings or zoom level, then change back. Computer info: - Ubuntu 20.04.1 - Fractional Scaling enabled - NVidia GeForce GTX 1080/PCIe/SSE2 - Gnome 3.36.3 - X11 - Samsung LU32J590 4K (3840x2160) @ 1.5x - Dell E2416Hb 1920x1080 rotated portrait left, right of Samsung ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-52.57-generic 5.4.65 Uname: Linux 5.4.0-52-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.gpus..02.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:02:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 435.21 Sun Aug 25 08:17:57 CDT 2019 GCC version: gcc version 9.3.0 (Ubuntu 9.3.0-17ubuntu1~20.04) ApportVersion: 2.20.11-0ubuntu27.10 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Wed Nov 4 09:31:17 2020 DistUpgraded: 2020-04-03 12:51:44,815 DEBUG Running PostInstallScript: './xorg_fix_proprietary.py' DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: NVIDIA Corporation GP104 [GeForce GTX 1080] [10de:1b80] (rev a1) (prog-if 00 [VGA controller]) Subsystem: eVga.com. Corp. GP104 [GeForce GTX 1080] [3842:6188] InstallationDate: Installed on 2018-04-28 (920 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-52-generic root=UUID=dfb5d6fd-4a4e-471d-bb00-77a6729533d8 ro quiet splash pci=nommconf vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to focal on 2020-04-03 (214 days ago) dmi.bios.date: 04/06/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P3.80 dmi.board.name: X99 Extreme4 dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP3.80:bd04/06/2018:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnX99Extreme4:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: To Be Filled By O.E.M. dmi.product.sku: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.8-0ubuntu1~20.04.1 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.4 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal possible-manual-nvidia-install ubuntu ** Description changed: One monitor is a 4K monitor scaled to 1.5x, the other is a normal 1920x1080 monitor scaled to 1x. While Firefox is already open, after logging into the lock screen, sometimes Firefox will lose the titlebar, address bar, buttons, and bookmark bar. The website being displayed will still show, however not all features are usable (right click menu, mouse icon doesn't change). Reproduction steps: - Change zoom level of one or more monitors to >1.0 but less than 2.0 (have not tested with non-fractional zooms) - Open Firefox and browse to any website - L
[Desktop-packages] [Bug 1898569] [NEW] laptop screen blank after reboot
Public bug reported: connected to external monitor. After a reboot the laptop screen is blank. Can't find a consistent way to get it back. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 5.4.0-48.52~18.04.1-generic 5.4.60 Uname: Linux 5.4.0-48-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.capabilities.gpu0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/capabilities/gpu0' .proc.driver.nvidia.capabilities.mig: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/capabilities/mig' .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 450.66 Wed Aug 12 19:42:48 UTC 2020 GCC version: gcc version 7.5.0 (Ubuntu 7.5.0-3ubuntu1~18.04) ApportVersion: 2.20.9-0ubuntu7.17 Architecture: amd64 CompositorRunning: None Date: Mon Oct 5 15:50:47 2020 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu DkmsStatus: nvidia, 450.66, 5.4.0-47-generic, x86_64: installed nvidia, 450.66, 5.4.0-48-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Device [8086:591b] (rev 04) (prog-if 00 [VGA controller]) Subsystem: Micro-Star International Co., Ltd. [MSI] Device [1462:11c9] Subsystem: Micro-Star International Co., Ltd. [MSI] GP107M [GeForce GTX 1050 Mobile] [1462:11c9] InstallationDate: Installed on 2020-06-03 (123 days ago) InstallationMedia: Ubuntu 18.04.4 LTS "Bionic Beaver" - Release amd64 (20200203.1) MachineType: Micro-Star International Co., Ltd. GP72 7RD ProcEnviron: LANG=en_GB.UTF-8 SHELL=/bin/bash TERM=xterm-256color LANGUAGE=en_GB:en PATH=(custom, no user) ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-48-generic root=/dev/mapper/ubuntu--vg-root ro nouveau.modeset=0 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/23/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: E1799IMS.324 dmi.board.asset.tag: Default string dmi.board.name: MS-1799 dmi.board.vendor: Micro-Star International Co., Ltd. dmi.board.version: REV:1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Micro-Star International Co., Ltd. dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrE1799IMS.324:bd03/23/2018:svnMicro-StarInternationalCo.,Ltd.:pnGP727RD:pvrREV1.0:rvnMicro-StarInternationalCo.,Ltd.:rnMS-1799:rvrREV1.0:cvnMicro-StarInternationalCo.,Ltd.:ct10:cvrN/A: dmi.product.family: GP dmi.product.name: GP72 7RD dmi.product.sku: 1799.3 dmi.product.version: REV:1.0 dmi.sys.vendor: Micro-Star International Co., Ltd. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2~18.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~18.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.8-0ubuntu1~18.04.1 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A 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: Mon Oct 5 15:30:42 2020 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic 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/1898569 Title: laptop screen blank after reboot Status in xorg package in Ubuntu: New Bug description: connected to external monitor. After a reboot the laptop screen is blank. Can't find a consistent way to get it back. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 5.4.0-48.52~18.04.1-generic 5.4.60 Uname: Linux 5.4.0-48-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.capabilities.gpu0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/capabilities/gpu0' .proc.driver.nvidia.capabilities.mig: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/capabilities/mig' .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 450.66 Wed Aug 12 19:42:48 UTC 2020 GCC version: gcc version 7.5.0 (Ubuntu 7.5.0-3ubuntu1~18.04) ApportVersion: 2.20.9-0ubuntu7.17 Architecture: amd64 Composi
[Desktop-packages] [Bug 1878194] Re: [Sennheiser HD 4.50 BTNC] Bluetooth headset not working when selecting HSP/HFP audio profile in Focal Fossa
I have the same issues with: - Cowin E7 Headset - Plugable USB-BT4LE Bluetooth dongle -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1878194 Title: [Sennheiser HD 4.50 BTNC] Bluetooth headset not working when selecting HSP/HFP audio profile in Focal Fossa Status in bluez package in Ubuntu: Confirmed Status in pulseaudio package in Ubuntu: Confirmed Bug description: After updating the release from Ubuntu 19.10 to 20.04, the bluetooth headset doesn't work anymore when HSP/HFP profile is selected. With Ubuntu 19.10 the headset was working, there was audio and the mic was perfect for video conferencing. [Steps to reproduce] 1. Connect headset (used blueman to setup and connect) 1.1. When connected the system automatically selects A2DP profile 2. Start playing audio (browser or other) 3. Change profile to HSP/HFP with pavucontrol (or blueman) 4. The audio disappears and microphone is not working (no input) 5. Optionally switch back to A2DP and the audio comes back [Expected] When switching to HSP/HFP the audio should keep playing and the microphone should start working [Notes] I tried with pavucontrol to switch between profiles while playing audio from a browser. As side note there's a led in the headset that still blinks when switching profile. I tried deleting the pulse folder under user's profile .config without success, also reinstalled packages and did a `sudo alsa force-reload` and rebooting several times. Note: not sure this is a duplicate of [Bug #1576559], it looks quite different since the profile changes but the headset stops working. [System info] Ubuntu: 20.04 - Linux 5.4.0-29-generic x86_64 pulseaudio: 1:13.99.1-1ubuntu3 bluez: 5.53-0ubuntu3 Headset: Sennheiser HD 4.50 BTNC To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1878194/+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 1877577] [NEW] Multi-monitor not behaving correctly when one display turned off
Public bug reported: The release is 20.04. The gnome-session version is 3.36.0-2ubuntu1. What is expected: 1. When either monitor is turned off, the monitor that is still on becomes the only monitor. 2. The mouse should work. What happens: 1. When the primary monitor is turned off only, the space is not updated. 2. When the non-primary monitor is turned off only, the mouse is frozen. This is https://bugs.launchpad.net/ubuntu/+source/gnome-session/+bug/1709159 Long version: I have two identical monitors hooked up on HDMI. Let's call them #1 and #2, with #1 left of #2. #1 is primary. Case 1: Turn off #1 (the primary), leaving #2 on: The display has not been updated to detect the turned off monitor. The mouse can move around on #2, including going to the #1 space even though #1 is turned off. When #1 is turned back on, everything works fine too. Case 2: Turn off #2 (the non-primary) leaving #1 on: The display *has* been updated to detect the turned off monitor. The mouse cannot move at all, even though the cursor is visible on #1. This is When #2 is turned back on, there is another display update (another flicker, plus a Pulseaudio notification of new sink detected since the monitor has built-in speakers). Other notes: My card is AMD RX480. Another user in https://bugs.launchpad.net/ubuntu/+source/gnome-session/+bug/1709159 is also using AMDGPU. ** Affects: gnome-session (Ubuntu) Importance: Undecided Status: New -- 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/1877577 Title: Multi-monitor not behaving correctly when one display turned off Status in gnome-session package in Ubuntu: New Bug description: The release is 20.04. The gnome-session version is 3.36.0-2ubuntu1. What is expected: 1. When either monitor is turned off, the monitor that is still on becomes the only monitor. 2. The mouse should work. What happens: 1. When the primary monitor is turned off only, the space is not updated. 2. When the non-primary monitor is turned off only, the mouse is frozen. This is https://bugs.launchpad.net/ubuntu/+source/gnome-session/+bug/1709159 Long version: I have two identical monitors hooked up on HDMI. Let's call them #1 and #2, with #1 left of #2. #1 is primary. Case 1: Turn off #1 (the primary), leaving #2 on: The display has not been updated to detect the turned off monitor. The mouse can move around on #2, including going to the #1 space even though #1 is turned off. When #1 is turned back on, everything works fine too. Case 2: Turn off #2 (the non-primary) leaving #1 on: The display *has* been updated to detect the turned off monitor. The mouse cannot move at all, even though the cursor is visible on #1. This is When #2 is turned back on, there is another display update (another flicker, plus a Pulseaudio notification of new sink detected since the monitor has built-in speakers). Other notes: My card is AMD RX480. Another user in https://bugs.launchpad.net/ubuntu/+source/gnome-session/+bug/1709159 is also using AMDGPU. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-session/+bug/1877577/+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 1832222] Re: using aakar font reboots printer
I re-tested in preparation for submitting the bug to Debian, and the problem has disappeared. Something has changed in the 10 months since my report, the package is still Version: 1.0-6ubuntu0.1, but plenty of other packages on the system have been updated. As there is no way of reproducing and investigating the root cause, I'm marking it as Invalid. ** Changed in: fonts-gujr-extra (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to fonts-gujr-extra in Ubuntu. https://bugs.launchpad.net/bugs/183 Title: using aakar font reboots printer Status in fonts-gujr-extra package in Ubuntu: Invalid Bug description: A user accidentally selected the aakar font for one cell of a spreadsheet containing English text. Printing the spreadsheet resulted in the printer displaying: Rebooting... followed by Initializing The result was the same for both printers tried: Samsung SL-M3820ND and HP Colour LaserJet CM1017 The spreadsheet was exported to a PDF, printing the PDF caused the same printer reboot. Opening the PDF in Libre Office Draw and printing caused the same printer reboot. If the font was changed to Liberation Sans, the file could be printed. A minimal Libre Office spreadsheet with the problem is attached. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fonts-gujr-extra/+bug/183/+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 1859369] [NEW] Gnome Cheese Overwrites gsettings
Public bug reported: I cannot get cheese to use my external USB webcam. cheese: 3.28.0-1ubuntu1 OS: 18.04.3 LTS on x86_64 gnome: 3.28.2 After plugging in the webcam, a new device appears at /dev/video2. Before running cheese, I set the camera setting as follows: $ gsettings set org.gnome.Cheese camera '/dev/video2' I then confirm the settings are correct: $ gsettings list-recursively org.gnome.Cheese org.gnome.Cheese countdown-duration 3 org.gnome.Cheese flash true org.gnome.Cheese photo-y-resolution 480 org.gnome.Cheese countdown true org.gnome.Cheese brightness 0.0 org.gnome.Cheese saturation 1.0 org.gnome.Cheese video-y-resolution 480 org.gnome.Cheese camera '/dev/video2' org.gnome.Cheese burst-repeat 4 org.gnome.Cheese photo-x-resolution 640 org.gnome.Cheese contrast 1.0 org.gnome.Cheese photo-path '' org.gnome.Cheese selected-effect 'identity' org.gnome.Cheese video-x-resolution 640 org.gnome.Cheese burst-delay 1000 org.gnome.Cheese hue 0.0 org.gnome.Cheese video-path '' I then run the Cheese app, open the Preferences menu and find that the Device field is greyed out and shows just one choice: "BisonCam, NB Pro: BisonCam, NB" I then run gsettings again: $ gsettings list-recursively org.gnome.Cheese org.gnome.Cheese countdown-duration 3 org.gnome.Cheese flash true org.gnome.Cheese photo-y-resolution 480 org.gnome.Cheese countdown true org.gnome.Cheese brightness 0.0 org.gnome.Cheese saturation 1.0 org.gnome.Cheese video-y-resolution 480 org.gnome.Cheese camera 'BisonCam, NB Pro: BisonCam, NB' org.gnome.Cheese burst-repeat 4 org.gnome.Cheese photo-x-resolution 640 org.gnome.Cheese contrast 1.0 org.gnome.Cheese photo-path '' org.gnome.Cheese selected-effect 'identity' org.gnome.Cheese video-x-resolution 640 org.gnome.Cheese burst-delay 1000 org.gnome.Cheese hue 0.0 org.gnome.Cheese video-path '' So, cheese seems to overwrite the gconf settings. I can't figure out how to get cheese to use my USB webcam! Additional info: $ sudo lsusb -v -s 003:036 Bus 003 Device 036: ID 0ac8:0302 Z-Star Microelectronics Corp. ZC0302 Webcam Device Descriptor: bLength18 bDescriptorType 1 bcdUSB 1.10 bDeviceClass0 (Defined at Interface level) bDeviceSubClass 0 bDeviceProtocol 0 bMaxPacketSize0 8 idVendor 0x0ac8 Z-Star Microelectronics Corp. idProduct 0x0302 ZC0302 Webcam bcdDevice1.00 iManufacturer 1 V Micro. Corp. iProduct2 PC Camera iSerial 0 bNumConfigurations 1 Configuration Descriptor: bLength 9 bDescriptorType 2 wTotalLength 336 bNumInterfaces 3 bConfigurationValue 1 iConfiguration 0 bmAttributes 0xa0 (Bus Powered) Remote Wakeup MaxPower 160mA Interface Descriptor: bLength 9 bDescriptorType 4 bInterfaceNumber0 bAlternateSetting 0 bNumEndpoints 2 bInterfaceClass 255 Vendor Specific Class bInterfaceSubClass255 Vendor Specific Subclass bInterfaceProtocol255 Vendor Specific Protocol iInterface 0 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x81 EP 1 IN bmAttributes1 Transfer TypeIsochronous Synch Type None Usage Type Data wMaxPacketSize 0x 1x 0 bytes bInterval 1 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x82 EP 2 IN bmAttributes3 Transfer TypeInterrupt Synch Type None Usage Type Data wMaxPacketSize 0x0008 1x 8 bytes bInterval 10 Interface Descriptor: bLength 9 bDescriptorType 4 bInterfaceNumber0 bAlternateSetting 1 bNumEndpoints 2 bInterfaceClass 255 Vendor Specific Class bInterfaceSubClass255 Vendor Specific Subclass bInterfaceProtocol255 Vendor Specific Protocol iInterface 0 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x81 EP 1 IN bmAttributes1 Transfer TypeIsochronous Synch Type None Usage Type Data wMaxPacketSize 0x0080 1x 128 bytes bInterval 1 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x82 EP 2 IN bmAttributes3 Transfer T
[Desktop-packages] [Bug 1832222] [NEW] using aakar font reboots printer
Public bug reported: A user accidentally selected the aakar font for one cell of a spreadsheet containing English text. Printing the spreadsheet resulted in the printer displaying: Rebooting... followed by Initializing The result was the same for both printers tried: Samsung SL-M3820ND and HP Colour LaserJet CM1017 The spreadsheet was exported to a PDF, printing the PDF caused the same printer reboot. Opening the PDF in Libre Office Draw and printing caused the same printer reboot. If the font was changed to Liberation Sans, the file could be printed. A minimal Libre Office spreadsheet with the problem is attached. ** Affects: fonts-gujr-extra (Ubuntu) Importance: Undecided Status: New ** Attachment added: "spreadsheet with font problem" https://bugs.launchpad.net/bugs/183/+attachment/5269913/+files/aakar_problem.ods -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to fonts-gujr-extra in Ubuntu. https://bugs.launchpad.net/bugs/183 Title: using aakar font reboots printer Status in fonts-gujr-extra package in Ubuntu: New Bug description: A user accidentally selected the aakar font for one cell of a spreadsheet containing English text. Printing the spreadsheet resulted in the printer displaying: Rebooting... followed by Initializing The result was the same for both printers tried: Samsung SL-M3820ND and HP Colour LaserJet CM1017 The spreadsheet was exported to a PDF, printing the PDF caused the same printer reboot. Opening the PDF in Libre Office Draw and printing caused the same printer reboot. If the font was changed to Liberation Sans, the file could be printed. A minimal Libre Office spreadsheet with the problem is attached. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fonts-gujr-extra/+bug/183/+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 1758247] Re: gnome-control-center is not open ubuntu 18.04
*** This bug is a duplicate of bug 1755536 *** https://bugs.launchpad.net/bugs/1755536 I recently switched from MATE to Gnome I experience the same problem. I have found that I can start gnome-control-center if I set the environment variable CLUTTER_BACKEND to wayland. You can start in in your shell like so: CLUTTER_BACKEND=wayland gnome-control-center If I check my current environment for clutter environment variables I see: $set | grep -i clutter CLUTTER_BACKEND=x11 CLUTTER_IM_MODULE=xim None of those are set in any of my dot files in my home, the culprit appears to be: X11/Xsession.d/99mate-environment:export CLUTTER_BACKEND=x11 -- 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/1758247 Title: gnome-control-center is not open ubuntu 18.04 Status in gnome-control-center package in Ubuntu: Confirmed Bug description: it is not openning and stuck ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-control-center 1:3.28.0-0ubuntu3 ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3 Uname: Linux 4.15.0-10-generic x86_64 ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Mar 23 13:13:11 2018 EcryptfsInUse: Yes InstallationDate: Installed on 2017-03-04 (384 days ago) InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215.2) SourcePackage: gnome-control-center UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1758247/+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 1755536] Re: gnome-control-center is not open ubuntu 18.04
I recently switched from MATE to Gnome I experience the same problem. I have found that I can start gnome-control-center if I set the environment variable CLUTTER_BACKEND to wayland. You can start in in your shell like so: CLUTTER_BACKEND=wayland gnome-control-center If I check my current environment for clutter environment variables I see: $set | grep -i clutter CLUTTER_BACKEND=x11 CLUTTER_IM_MODULE=xim None of those are set in any of my dot files in my home, the culprit appears to be: X11/Xsession.d/99mate-environment:export CLUTTER_BACKEND=x11 -- 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/1755536 Title: gnome-control-center is not open ubuntu 18.04 Status in gnome-control-center package in Ubuntu: Expired Bug description: gnome-control-center is not working when open. it will not open on ubuntu 18.04 even after reinstall ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-control-center 1:3.27.92-1ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3 Uname: Linux 4.15.0-10-generic x86_64 ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Mar 13 23:28:27 2018 EcryptfsInUse: Yes InstallationDate: Installed on 2017-03-04 (374 days ago) InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215.2) SourcePackage: gnome-control-center UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1755536/+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 1829667] [NEW] Autostart doesn't work over native -protocol-tcp
Public bug reported: This isn't necessarily a bug, but when receiving audio through module- native-protocol-tcp the server does not autostart when audio is being played on the client. The result is that the server must be started manually on the receiving machine before sound is output on the sending machine, unless the exit-idle-time on the server is set to -1. I am streaming over the localhost from withing a chroot, and this it is a serious resource drain to have exit-idle disabled. Is there a way to configure autostart when using native-protocol-tcp? ** Affects: pulseaudio (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1829667 Title: Autostart doesn't work over native -protocol-tcp Status in pulseaudio package in Ubuntu: New Bug description: This isn't necessarily a bug, but when receiving audio through module- native-protocol-tcp the server does not autostart when audio is being played on the client. The result is that the server must be started manually on the receiving machine before sound is output on the sending machine, unless the exit-idle-time on the server is set to -1. I am streaming over the localhost from withing a chroot, and this it is a serious resource drain to have exit-idle disabled. Is there a way to configure autostart when using native-protocol-tcp? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1829667/+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 1164016] Re: restore type-ahead find
+1. Type-ahead is basic expected functionality of a file browser. -- 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/1164016 Title: restore type-ahead find Status in Nautilus: Expired Status in nautilus package in Ubuntu: Fix Released Status in ubuntu-settings package in Ubuntu: Fix Released Bug description: GNOME removed type-ahead find in Nautilus 3.6, not without controversy: https://mail.gnome.org/archives/nautilus- list/2012-August/msg2.html Now when you type in a Nautilus window, Nautilus immediately performs a search in the current directory and all its subdirectories. I personally find this annoying. If I want to search, I'll click the search icon. Often I'm looking at a long directory listing and simply want to jump to a certain point in it, and type-ahead find works great for that. Would Ubuntu consider patching type-ahead find back in? To manage notifications about this bug go to: https://bugs.launchpad.net/nautilus/+bug/1164016/+subscriptions -- Mailing list: https://launchpad.net/~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 1666681] Re: Restore interactive_search.patch (type-ahead search)
Lack of type-ahead is unbearable. -- 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/181 Title: Restore interactive_search.patch (type-ahead search) Status in nautilus package in Ubuntu: Won't Fix Bug description: Nautilus dropped the popular type-ahead search feature years ago. Ubuntu has been carrying a patch to revert that change. See bug 1164016 for the original LP bug and patch proposal. Nautilus is now under very active development. During the 3.22 cycle, that patch needed to be rebased. I tried to do it and what I came up with caused a crash (it didn't really crash for me, but ricotz and some others experienced it) and the first letter typed activated type- ahead search but the first letter was dropped. In other words, you would need to type "ddow" to activate the Downloads folder instead of just "dow" like in previous releases. (LP: #1635988) I did that rebase in October 2016 and no one has stepped up then to improve the patch. The Nautilus maintainer csoriano has said that the slots and views changed significantly during 3.22 and will likely be refactored more in the future. If there's no one available to maintain the patch, unfortunately, we'll eventually have to drop the patch to not be stuck on an ancient version of Nautilus. I am proposing that we do this at the start of the 17.10 development cycle. This gives 6 months for a developer to step up and try to fix the patch and 12 months before 18.04 LTS. Other Items === - For better performance with the built-in search, we need to reconsider avoiding tracker in Unity (LP: #176) - There is an option in Preferences for users to disable searching in subfolders. I don't think we want to do that by default but maybe it can help some people. The current Nautilus 3.24 packaging is in the GNOME3 Staging PPA with this patch now disabled. https://launchpad.net/~gnome3-team/+archive/ubuntu/gnome3-staging/+packages?field.series_filter=zesty To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/181/+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 871542] Re: Right click on bookmark items doesn't work.
I just wish to clarify that this bug refers to what happens when one attempts to right-click the bookmark items in the drop-down menuy that appear after clicking on the menu bar item "Bookmarks". This does not refer to right-clicking on any bookmark that exists inside the applet that appears after clicking "Show All Bookmarks" (i.e. the "Library" applet.) -- 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/871542 Title: Right click on bookmark items doesn't work. Status in firefox package in Ubuntu: Confirmed Bug description: I'm using Ubuntu 11.04, Firefox 7.0.1. Right click on a bookmark item should cause a context menu to pop up from which user can choose what to do. But when I right click on any bookmark item, it just open that item as if I clicked the left button instead of the right button. ProblemType: Bug DistroRelease: Ubuntu 11.04 Package: firefox 7.0.1+build1+nobinonly-0ubuntu0.11.04.1 ProcVersionSignature: Ubuntu 2.6.38-11.50-generic 2.6.38.8 Uname: Linux 2.6.38-11-generic i686 NonfreeKernelModules: nvidia AddonCompatCheckDisabled: False AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.23. Architecture: i386 ArecordDevices: List of CAPTURE Hardware Devices card 0: Intel [HDA Intel], device 0: CONEXANT Analog [CONEXANT Analog] Subdevices: 1/1 Subdevice #0: subdevice #0 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: spirit 1515 F pulseaudio /dev/snd/pcmC0D0p: spirit 1515 F...m pulseaudio BuildID: 20110928224103 CRDA: Error: [Errno 2] No such file or directory Card0.Amixer.info: Card hw:0 'Intel'/'HDA Intel at 0xf450 irq 48' Mixer name : 'Conexant CX20561 (Hermosa)' Components : 'HDA:14f15051,17aa3c2d,0010' Controls : 16 Simple ctrls : 8 Channel: release Date: Mon Oct 10 08:47:44 2011 ForcedLayersAccel: False IfupdownConfig: auto lo iface lo inet loopback InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release i386 (20110427.1) IpRoute: 222.39.36.1 dev ppp0 proto kernel scope link src 222.39.37.6 169.254.0.0/16 dev ppp0 scope link metric 1000 default via 222.39.36.1 dev ppp0 proto static ProcEnviron: LANGUAGE=en_US:en LANG=en_US.UTF-8 SHELL=/bin/bash Profiles: Profile0 (Default) - LastVersion=7.0.1/20110928224103 (Running) RunningIncompatibleAddons: False SourcePackage: firefox UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/17/2008 dmi.bios.vendor: LENOVO dmi.bios.version: 0DCN54WW dmi.board.name: LE8 dmi.board.vendor: Lenovo dmi.board.version: Rev 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Lenovo dmi.chassis.version: Rev 1.0 dmi.modalias: dmi:bvnLENOVO:bvr0DCN54WW:bd11/17/2008:svnLENOVO:pnZHAOYANGK43:pvrRev1.0:rvnLenovo:rnLE8:rvrRev1.0:cvnLenovo:ct10:cvrRev1.0: dmi.product.name: ZHAOYANG K43 dmi.product.version: Rev 1.0 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/871542/+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 871542] Re: Right click on bookmark items doesn't work.
The problem still exists in Firefox 61.0.1 (64-bit) under Ubuntu 16.04LTS. -- 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/871542 Title: Right click on bookmark items doesn't work. Status in firefox package in Ubuntu: Incomplete Bug description: I'm using Ubuntu 11.04, Firefox 7.0.1. Right click on a bookmark item should cause a context menu to pop up from which user can choose what to do. But when I right click on any bookmark item, it just open that item as if I clicked the left button instead of the right button. ProblemType: Bug DistroRelease: Ubuntu 11.04 Package: firefox 7.0.1+build1+nobinonly-0ubuntu0.11.04.1 ProcVersionSignature: Ubuntu 2.6.38-11.50-generic 2.6.38.8 Uname: Linux 2.6.38-11-generic i686 NonfreeKernelModules: nvidia AddonCompatCheckDisabled: False AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.23. Architecture: i386 ArecordDevices: List of CAPTURE Hardware Devices card 0: Intel [HDA Intel], device 0: CONEXANT Analog [CONEXANT Analog] Subdevices: 1/1 Subdevice #0: subdevice #0 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: spirit 1515 F pulseaudio /dev/snd/pcmC0D0p: spirit 1515 F...m pulseaudio BuildID: 20110928224103 CRDA: Error: [Errno 2] No such file or directory Card0.Amixer.info: Card hw:0 'Intel'/'HDA Intel at 0xf450 irq 48' Mixer name : 'Conexant CX20561 (Hermosa)' Components : 'HDA:14f15051,17aa3c2d,0010' Controls : 16 Simple ctrls : 8 Channel: release Date: Mon Oct 10 08:47:44 2011 ForcedLayersAccel: False IfupdownConfig: auto lo iface lo inet loopback InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release i386 (20110427.1) IpRoute: 222.39.36.1 dev ppp0 proto kernel scope link src 222.39.37.6 169.254.0.0/16 dev ppp0 scope link metric 1000 default via 222.39.36.1 dev ppp0 proto static ProcEnviron: LANGUAGE=en_US:en LANG=en_US.UTF-8 SHELL=/bin/bash Profiles: Profile0 (Default) - LastVersion=7.0.1/20110928224103 (Running) RunningIncompatibleAddons: False SourcePackage: firefox UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/17/2008 dmi.bios.vendor: LENOVO dmi.bios.version: 0DCN54WW dmi.board.name: LE8 dmi.board.vendor: Lenovo dmi.board.version: Rev 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Lenovo dmi.chassis.version: Rev 1.0 dmi.modalias: dmi:bvnLENOVO:bvr0DCN54WW:bd11/17/2008:svnLENOVO:pnZHAOYANGK43:pvrRev1.0:rvnLenovo:rnLE8:rvrRev1.0:cvnLenovo:ct10:cvrRev1.0: dmi.product.name: ZHAOYANG K43 dmi.product.version: Rev 1.0 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/871542/+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 1523100] Re: Alsa not detecting internal microphone [ALC255] (Realtek)
Same problem here with Acer Aspire VN7-792G and ALC255. Internal mic not detected and hdajackretask not working. This model also has a separate mic-jack and a headphone-jack and an internal mic. The internal mic isn't detected and not working. -- 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/1523100 Title: Alsa not detecting internal microphone [ALC255] (Realtek) Status in alsa-driver package in Ubuntu: Confirmed Bug description: I've just installed Ubuntu 16.04 alongside Windows 10 on a 64bit Acer Aspire VN7-792G and noticed, that the internal microphone doesn't work. The computer has been released a couple of months ago and it's Intel Skylake -based with a Sunrise Point -based motherboard. INFO: The problem exists in Ubuntu 15.10 too, only microphone jack detected. Currently using Ubuntu 16.04 for proper hardware support. Alsa reports the audio device to be: Card: HDA Intel PCH Chip: Intel Skylake HDMI The speakers are working fine, but both alsamixer and pavucontrol (Pulseaudio Volume Control) raport the unplugged external microphone connector as the only sound input. I have tried many of the alsa model configurations (options snd-hda- intel model=something) without success, alsa finds only the microphone jack, which works fine when I plug an external microphone in it. Here's some info: lspci | grep -I audio: 00:1f.3 Multimedia audio controller: Intel Corporation Sunrise Point-H HD Audio (rev 31) cat /proc/asound/cards: 0 [PCH]: HDA-Intel - HDA Intel PCH HDA Intel PCH at 0x8432 irq 128 And a clip from dmesg | grep snd: [3.019164] snd_hda_intel :00:1f.3: bound :00:02.0 (ops i915_audio_component_bind_ops [i915]) [3.047505] snd_hda_codec_realtek hdaudioC0D0: autoconfig for ALC255: line_outs=1 (0x14/0x0/0x0/0x0/0x0) type:speaker [3.047508] snd_hda_codec_realtek hdaudioC0D0:speaker_outs=0 (0x0/0x0/0x0/0x0/0x0) [3.047510] snd_hda_codec_realtek hdaudioC0D0:hp_outs=1 (0x21/0x0/0x0/0x0/0x0) [3.047511] snd_hda_codec_realtek hdaudioC0D0:mono: mono_out=0x0 [3.047512] snd_hda_codec_realtek hdaudioC0D0:dig-out=0x1e/0x0 [3.047512] snd_hda_codec_realtek hdaudioC0D0:inputs: [3.047514] snd_hda_codec_realtek hdaudioC0D0: Mic=0x1a One problem is that I can't find any model options (options snd-hda- intel model=something) or other parameters for the card's model (ALC255), I suppose this issue is relatively new. /Dennis --- ApportVersion: 2.19.2-0ubuntu6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: dennis 1180 F pulseaudio CurrentDesktop: GNOME DistroRelease: Ubuntu 16.04 InstallationDate: Installed on 2015-11-11 (23 days ago) InstallationMedia: Ubuntu-GNOME 16.04 LTS "Xenial Xerus" - Alpha amd64 (20151110) Package: alsa-driver (not installed) ProcVersionSignature: Ubuntu 4.2.0-19.23-generic 4.2.6 Tags: xenial Uname: Linux 4.2.0-19-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm bumblebee cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 09/25/2015 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.02 dmi.board.asset.tag: No Asset Tag dmi.board.name: Aspire VN7-792G dmi.board.vendor: Acer dmi.board.version: V1.02 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: V1.02 dmi.modalias: dmi:bvnInsydeCorp.:bvrV1.02:bd09/25/2015:svnAcer:pnAspireVN7-792G:pvrV1.02:rvnAcer:rnAspireVN7-792G:rvrV1.02:cvnAcer:ct10:cvrV1.02: dmi.product.name: Aspire VN7-792G dmi.product.version: V1.02 dmi.sys.vendor: Acer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1523100/+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 1131858] Re: file operations window hangs after completion of file transfer to FAT file system from ext4 file system
*** This bug is a duplicate of bug 1001579 *** https://bugs.launchpad.net/bugs/1001579 This is still happening in 16.04LTS. -- 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/1131858 Title: file operations window hangs after completion of file transfer to FAT file system from ext4 file system Status in nautilus package in Ubuntu: Confirmed Bug description: Using 12.04 and attempting to drag-and-drop a large file from my Downloads folder to a USB thumb drive, the File Operations window displays a full progress bar and the text "777.9 MB of 777.9 MB". This dialog box hangs for about five minutes, during which time I ran 'ubuntu-bug nautilus' in the hopes that the problem details were captured. This bug seems identical to bug 612076 in 10.04 which was closed due to inactivity. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: nautilus 1:3.4.2-0ubuntu6 ProcVersionSignature: Ubuntu 3.2.0-38.61-generic 3.2.37 Uname: Linux 3.2.0-38-generic x86_64 ApportVersion: 2.0.1-0ubuntu17.1 Architecture: amd64 Date: Fri Feb 22 11:16:35 2013 GsettingsChanges: org.gnome.nautilus.window-state geometry '1202x621+476+430' InstallationMedia: Ubuntu 12.04.1 LTS "Precise Pangolin" - Release amd64 (20120822.4) MarkForUpload: True ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1131858/+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 1682193] Re: Mouse acceleration significantly reduced after upgrade to 17.04
xinput didn't work for me at all. Neither was changing the sensitivity in the default mouse application or in gpointing-device-settings. What DID work for me was change the value in "/sys/devices/platform/i8042/serio1/sensitivity" to 200. It worked immediately. Good luck. -- 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/1682193 Title: Mouse acceleration significantly reduced after upgrade to 17.04 Status in xorg package in Ubuntu: Confirmed Bug description: My external Logitech USB mouse was behaving nicely under 16.10 but after upgrade to 17.04 it has slowed down to a crawl. Settings slidebars are set at the maximum acceleration, but it only affects the touch pad, the mouse is extremely slow. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1682193/+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 1693397] [NEW] package emacsen-common 2.0.8 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1
Public bug reported: This was encountered when running 16.02 upgrade. ProblemType: Package DistroRelease: Ubuntu 16.04 Package: emacsen-common 2.0.8 ProcVersionSignature: Ubuntu 4.4.0-78.99-generic 4.4.62 Uname: Linux 4.4.0-78-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.6 Architecture: amd64 Date: Wed May 24 17:39:58 2017 Dependencies: ErrorMessage: subprocess installed post-installation script returned error exit status 1 InstallationDate: Installed on 2015-05-22 (734 days ago) InstallationMedia: Ubuntu 12.04.1 LTS "Precise Pangolin" - Release amd64 (20120823.1) PackageArchitecture: all RelatedPackageVersions: dpkg 1.18.4ubuntu1.2 apt 1.2.20 SourcePackage: emacsen-common Title: package emacsen-common 2.0.8 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 UpgradeStatus: Upgraded to xenial on 2017-05-25 (0 days ago) ** Affects: emacsen-common (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package xenial -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to emacsen-common in Ubuntu. https://bugs.launchpad.net/bugs/1693397 Title: package emacsen-common 2.0.8 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 Status in emacsen-common package in Ubuntu: New Bug description: This was encountered when running 16.02 upgrade. ProblemType: Package DistroRelease: Ubuntu 16.04 Package: emacsen-common 2.0.8 ProcVersionSignature: Ubuntu 4.4.0-78.99-generic 4.4.62 Uname: Linux 4.4.0-78-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.6 Architecture: amd64 Date: Wed May 24 17:39:58 2017 Dependencies: ErrorMessage: subprocess installed post-installation script returned error exit status 1 InstallationDate: Installed on 2015-05-22 (734 days ago) InstallationMedia: Ubuntu 12.04.1 LTS "Precise Pangolin" - Release amd64 (20120823.1) PackageArchitecture: all RelatedPackageVersions: dpkg 1.18.4ubuntu1.2 apt 1.2.20 SourcePackage: emacsen-common Title: package emacsen-common 2.0.8 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 UpgradeStatus: Upgraded to xenial on 2017-05-25 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/emacsen-common/+bug/1693397/+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 1677085] [NEW] package cups-daemon (not installed) failed to install/upgrade: subprocess new pre-removal script returned error exit status 1
*** This bug is a duplicate of bug 1676881 *** https://bugs.launchpad.net/bugs/1676881 Public bug reported: I was just booting up and got the error... and the options to report a bug... ProblemType: Package DistroRelease: Ubuntu 16.04 Package: cups-daemon (not installed) ProcVersionSignature: Ubuntu 4.4.0-66.87-generic 4.4.44 Uname: Linux 4.4.0-66-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.5 Architecture: amd64 Date: Mon Mar 27 08:56:36 2017 ErrorMessage: subprocess new pre-removal script returned error exit status 1 InstallationDate: Installed on 2017-03-27 (1 days ago) InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) RelatedPackageVersions: dpkg 1.18.4ubuntu1.1 apt 1.2.19 SourcePackage: cups Title: package cups-daemon (not installed) failed to install/upgrade: subprocess new pre-removal script returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: cups (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package xenial -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/1677085 Title: package cups-daemon (not installed) failed to install/upgrade: subprocess new pre-removal script returned error exit status 1 Status in cups package in Ubuntu: New Bug description: I was just booting up and got the error... and the options to report a bug... ProblemType: Package DistroRelease: Ubuntu 16.04 Package: cups-daemon (not installed) ProcVersionSignature: Ubuntu 4.4.0-66.87-generic 4.4.44 Uname: Linux 4.4.0-66-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.5 Architecture: amd64 Date: Mon Mar 27 08:56:36 2017 ErrorMessage: subprocess new pre-removal script returned error exit status 1 InstallationDate: Installed on 2017-03-27 (1 days ago) InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) RelatedPackageVersions: dpkg 1.18.4ubuntu1.1 apt 1.2.19 SourcePackage: cups Title: package cups-daemon (not installed) failed to install/upgrade: subprocess new pre-removal script returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1677085/+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 1181902] Re: Nouveau driver glitch on Ubuntu 13.04 will cause system to freeze under certain conditions
Can confirm that nouveau.noaccel=1 solved the lockup in my desktop with "GeForce 6150SE nForce 430". But if you need some graphical effects or things like that, forget! You'll have an system 'not bricked', but really ugly. I'm not using Ubuntu anymore, but last year (with another distro) I give nouveau a try and the same problem that I used to have in fresh Ubuntu install 4 years back showed. This glitch in nouveau is very annoying. NVIDIA proprietary driver (304xx-lts) don't have a good performance with glx (i.e. if you have compton and some little desktop effects, the delay is huge). Same machine, same NVIDIA driver, but this time with Windows: the desktop don't have such a poor performance. Nothing is perfect... I have to buy a new computer anyway. ¯\_(ツ)_/¯ -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-video-nouveau in Ubuntu. https://bugs.launchpad.net/bugs/1181902 Title: Nouveau driver glitch on Ubuntu 13.04 will cause system to freeze under certain conditions Status in xserver-xorg-video-nouveau package in Ubuntu: Incomplete Bug description: Hi, This only happens to Ubuntu 13.04, as my GeForce 6150SE card was working fine for Ubuntu 12.10. The Nouveau driver glitch will cause my whole system to freeze under certain conditions. I first get my system freeze when starting virtualbox, which is installed from the offical Oracle virtualbox PPA. Duplicated several times -- Freshly boot into X, then start virtualbox from within xterm via "virtualbox &", 2 seconds later my whole system freeze up. Google search indicated that it might be cause by the offical Oracle virtualbox PPA, so I followed the advice to switch to the offical Ubuntu virtualbox from the software center, but get into system freeze doing exactly the same thing. Duplicated several times as well. I was about to conclude that it is the virtualbox's problem when I suddenly remember that I've got into such system freeze before doing something entirely different, because the symptom is exactly the same. So I tried again -- "startx -- :1" to get me into another X session, and quit. Yes, then and there, I get into such system freeze again. The symptom is that the display turned black, then a random pattern tiled across the whole screen. Installing the closed source additional driver (nvidia) to replace the Nouveau driver solve the problem, which in turn proved that my suspicion was right -- it *is* the Nouveau driver that is causing the problem. Thanks PS. Comparing with the previous Xorg.1.log, the lines that didn't get output are: (II) NOUVEAU(0): EDID vendor "ACR", prod id 426 (II) NOUVEAU(0): Using EDID range info for horizontal sync (II) NOUVEAU(0): Using EDID range info for vertical refresh (II) NOUVEAU(0): Printing DDC gathered Modelines: . . . The whole unloading part (filtered by "sed 's/\[[^]]*]//'") of my previous Xorg.1.log is at http://paste.debian.net/5260/, the whole un- filtered file is at http://paste.debian.net/5261/. Here is my GeForce 6150SE card: $ lspci | grep VGA 00:0d.0 VGA compatible controller: NVIDIA Corporation C61 [GeForce 6150SE nForce 430] (rev a2) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-nouveau/+bug/1181902/+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 1672160] Re: LibreOffice Calc Cannot Select Copy Radio Button in Move/Copy Sheet Dialog
Sorry. The problem was because the installed build was for an earlier version of OS (i.e Trusty instead of Xenial). I had upgraded my OS from 14.04 to 16.04 but the application did not automatically upgrade as well (this was not obvious to me and the broken behaviour was a surprise). Anyway, I realized that the build was for a different OS. I removed the original install and re-installed deb from libreoffice.org and the problem went away. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libreoffice in Ubuntu. https://bugs.launchpad.net/bugs/1672160 Title: LibreOffice Calc Cannot Select Copy Radio Button in Move/Copy Sheet Dialog Status in libreoffice package in Ubuntu: Invalid Bug description: When I right-click on a sheet tab and select "Move or Copy Sheet...", and I click on the Copy radio button, the button does not get filled in so it loks as if I cannot copy. However, when I do click on the button, the New Name field does get automatically filled in with a new name (the original name appended with an underscore and sequential number). Then, if I click OK, the new sheet is created. So, the operation does seem to work in the end. The Move button does not get filled in either. Therefore, it appears as if there is something wrong with the radio button widget. The problem is minor because there is no data loss; nevertheless, the behaviour is at least disconcerting. LibreOffice Version: 5.3.0.3 Build ID: 1:5.3.0~rc3-0ubuntu1~trusty1.1 CPU Threads: 8; OS Version: Linux 4.4; UI Render: default; VCL: gtk3; Layout Engine: new; Locale: en-CA (en_CA.UTF-8); Calc: group OS: Ubuntu 16.04.2 LTS (Xenial Xerus) Question: should I also open a bug at https://bugs.freedesktop.org? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1672160/+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 1672160] Re: LibreOffice Calc Cannot Select Copy Radio Button in Move/Copy Sheet Dialog
** Changed in: libreoffice (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libreoffice in Ubuntu. https://bugs.launchpad.net/bugs/1672160 Title: LibreOffice Calc Cannot Select Copy Radio Button in Move/Copy Sheet Dialog Status in libreoffice package in Ubuntu: Invalid Bug description: When I right-click on a sheet tab and select "Move or Copy Sheet...", and I click on the Copy radio button, the button does not get filled in so it loks as if I cannot copy. However, when I do click on the button, the New Name field does get automatically filled in with a new name (the original name appended with an underscore and sequential number). Then, if I click OK, the new sheet is created. So, the operation does seem to work in the end. The Move button does not get filled in either. Therefore, it appears as if there is something wrong with the radio button widget. The problem is minor because there is no data loss; nevertheless, the behaviour is at least disconcerting. LibreOffice Version: 5.3.0.3 Build ID: 1:5.3.0~rc3-0ubuntu1~trusty1.1 CPU Threads: 8; OS Version: Linux 4.4; UI Render: default; VCL: gtk3; Layout Engine: new; Locale: en-CA (en_CA.UTF-8); Calc: group OS: Ubuntu 16.04.2 LTS (Xenial Xerus) Question: should I also open a bug at https://bugs.freedesktop.org? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1672160/+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 1517046] Re: Unable to set 1920x1080 resolution in Ubuntu 16.04 as a VMWare Fusion guest
I've changed my HDMI cable and discovered that part of the problem or the problem as a whole is due to the HDMI cable that I was using. The monitor stated that the frequency was out of range when I used a DVI adapter so I tried playing around with various frequencies to no avail. Finally I switched to a sturdier HDMI cable, with the DVI adapter as well, and the picture shows up at 1920x1080@60hz again. It's very frustrating to find out that a poorly manufactured HDMI cable can work in some computers and monitors but not others. It would be nice if Ubuntu were a little more forgiving, but I'm glad to have found a solution. -- 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/1517046 Title: Unable to set 1920x1080 resolution in Ubuntu 16.04 as a VMWare Fusion guest Status in xorg-server package in Ubuntu: New Bug description: I'm testing Ubuntu 16.04 as a guest of a VMWare Fusion guest under Mac OS X 10.11.1. All works fine, but I'm unable to set 1920x1080 resolution (monitor native) on external display. I can do 1920x1600 or more, but not 1920x1080. I have tried open-vm-tools and vmware-tools, but problem persists. On display-setting, the monitor is marked as unknown display. 1) Ubuntu Xenial Xerus (development branch) - release 16.04 2) xorg 1:7.7+12ubuntu1 3) Looking to change external display resolution as 1920x1080 4) I have not found the 1920x1080 setting To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1517046/+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 1517046] Re: Unable to set 1920x1080 resolution in Ubuntu 16.04 as a VMWare Fusion guest
I'm sorry, I made a mistake and said it doesn't list the native resolution. This was wrong. The displays application lists the native 1920x1080 but the display goes blank when this is selected. Using a lower setting (1280x720) works. Adding a higher setting (2048x1152) fails for obvious reasons. -- 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/1517046 Title: Unable to set 1920x1080 resolution in Ubuntu 16.04 as a VMWare Fusion guest Status in xorg-server package in Ubuntu: New Bug description: I'm testing Ubuntu 16.04 as a guest of a VMWare Fusion guest under Mac OS X 10.11.1. All works fine, but I'm unable to set 1920x1080 resolution (monitor native) on external display. I can do 1920x1600 or more, but not 1920x1080. I have tried open-vm-tools and vmware-tools, but problem persists. On display-setting, the monitor is marked as unknown display. 1) Ubuntu Xenial Xerus (development branch) - release 16.04 2) xorg 1:7.7+12ubuntu1 3) Looking to change external display resolution as 1920x1080 4) I have not found the 1920x1080 setting To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1517046/+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 1517046] Re: Unable to set 1920x1080 resolution in Ubuntu 16.04 as a VMWare Fusion guest
@yuval can fix the issue by creating a ~/.xprofile file with the xrandr lines (change the lines to match your configuration): xrandr --newmode "1920x1080" 173.00 1920 2048 2248 2576 1080 1083 1088 1120 -hsync +vsync xrandr --addmode eDP-1 1920x1080 use "cvt 1920 1080 60" to get the --newmode line I am getting similar results as OP with an HP 2711x using Ubuntu 17.04 beta. The monitor is detected but it doesn't list the native 1920 x 1080 @ 60Hz resolution. Adding the resolution with xrandr makes the external monitor go black, but the displays application still shows it on and connected. Two other new Dell monitors won't detect at all, however one is using USB-C->HDMI to HDMI->DP adapters which I think is causing issues. The other is using Thinkpad's DisplayLink with the latest drivers. -- 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/1517046 Title: Unable to set 1920x1080 resolution in Ubuntu 16.04 as a VMWare Fusion guest Status in xorg-server package in Ubuntu: New Bug description: I'm testing Ubuntu 16.04 as a guest of a VMWare Fusion guest under Mac OS X 10.11.1. All works fine, but I'm unable to set 1920x1080 resolution (monitor native) on external display. I can do 1920x1600 or more, but not 1920x1080. I have tried open-vm-tools and vmware-tools, but problem persists. On display-setting, the monitor is marked as unknown display. 1) Ubuntu Xenial Xerus (development branch) - release 16.04 2) xorg 1:7.7+12ubuntu1 3) Looking to change external display resolution as 1920x1080 4) I have not found the 1920x1080 setting To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1517046/+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 1672160] [NEW] LibreOffice Calc Cannot Select Copy Radio Button in Move/Copy Sheet Dialog
Public bug reported: When I right-click on a sheet tab and select "Move or Copy Sheet...", and I click on the Copy radio button, the button does not get filled in so it loks as if I cannot copy. However, when I do click on the button, the New Name field does get automatically filled in with a new name (the original name appended with an underscore and sequential number). Then, if I click OK, the new sheet is created. So, the operation does seem to work in the end. The Move button does not get filled in either. Therefore, it appears as if there is something wrong with the radio button widget. The problem is minor because there is no data loss; nevertheless, the behaviour is at least disconcerting. LibreOffice Version: 5.3.0.3 Build ID: 1:5.3.0~rc3-0ubuntu1~trusty1.1 CPU Threads: 8; OS Version: Linux 4.4; UI Render: default; VCL: gtk3; Layout Engine: new; Locale: en-CA (en_CA.UTF-8); Calc: group OS: Ubuntu 16.04.2 LTS (Xenial Xerus) Question: should I also open a bug at https://bugs.freedesktop.org? ** Affects: libreoffice (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libreoffice in Ubuntu. https://bugs.launchpad.net/bugs/1672160 Title: LibreOffice Calc Cannot Select Copy Radio Button in Move/Copy Sheet Dialog Status in libreoffice package in Ubuntu: New Bug description: When I right-click on a sheet tab and select "Move or Copy Sheet...", and I click on the Copy radio button, the button does not get filled in so it loks as if I cannot copy. However, when I do click on the button, the New Name field does get automatically filled in with a new name (the original name appended with an underscore and sequential number). Then, if I click OK, the new sheet is created. So, the operation does seem to work in the end. The Move button does not get filled in either. Therefore, it appears as if there is something wrong with the radio button widget. The problem is minor because there is no data loss; nevertheless, the behaviour is at least disconcerting. LibreOffice Version: 5.3.0.3 Build ID: 1:5.3.0~rc3-0ubuntu1~trusty1.1 CPU Threads: 8; OS Version: Linux 4.4; UI Render: default; VCL: gtk3; Layout Engine: new; Locale: en-CA (en_CA.UTF-8); Calc: group OS: Ubuntu 16.04.2 LTS (Xenial Xerus) Question: should I also open a bug at https://bugs.freedesktop.org? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1672160/+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 1086357] Re: Bit Fields appear as Varchar using libreoffice-mysqlconnector
Since 2012 I have worked around this issue by using ODBC to connect to MySQL from LibreOffice. However I have now upgraded to Ubuntu 16.04 which no longer has the ODBC package libmyodbc so I have had to revert to the mysql connector to allow connecting tC MySQL tables using LibreOffice Base Columns defined Bit(1) in MySQL still show incorrectly as VarChar in LibreOffice Base and cannot be maintained via LibreOffice Base. I have found a workable alternative. In Base, if I edit the table column and change the column type Yes/No Boo, the table column type updates to TinyInt. The column still provides the flag capability in my queries and can now be updated in Base via Tables or Forms. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libreoffice in Ubuntu. https://bugs.launchpad.net/bugs/1086357 Title: Bit Fields appear as Varchar using libreoffice-mysqlconnector Status in libreoffice package in Ubuntu: New Bug description: After changing from using ODBC to MySQL Connector extension to connect to MySQL databases, I noticed some columns defined as Bit fields did not behave correctly. Field data would not modify. Editing the tables in Libreoffice I have found that columns which are defined as Bit in MySQL are shown as Field Type text VARCHAR . Ubuntu 12.04 libreoffice 1:3.5.4-0ubuntu1.1 (LibreOffice 3.5.4.2 Build ID: 350m1(Build:2)) libreoffice-mysql-connector 1.0.1+LibO3.5.4-0ubuntu1.1 mysql-client 5.5.28-0ubuntu0.12.04.2 mysql-server 5.5.28-0ubuntu0.12.04.2 --- ApportVersion: 2.0.1-0ubuntu15 Architecture: amd64 DistroRelease: Ubuntu 12.04 InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 (20120425) MarkForUpload: True NonfreeKernelModules: nvidia Package: libreoffice 1:3.5.4-0ubuntu1.1 PackageArchitecture: amd64 ProcEnviron: LANGUAGE=en_GB:en TERM=xterm PATH=(custom, no user) LANG=en_GB.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 3.2.0-34.53-generic 3.2.33 Tags: precise running-unity Uname: Linux 3.2.0-34-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1086357/+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 1430769] Re: Does not detect hidden WiFi on first attempt
Confirming this FWIW, arale r242. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to wpasupplicant in Ubuntu. https://bugs.launchpad.net/bugs/1430769 Title: Does not detect hidden WiFi on first attempt Status in Canonical System Image: Confirmed Status in indicator-network package in Ubuntu: Confirmed Status in ubuntu-system-settings package in Ubuntu: Invalid Status in wpasupplicant package in Ubuntu: Confirmed Bug description: The WiFi network I use at home is a hidden one. While it works with my Ubuntu Phone, I always have to toggle WiFi on and off about 3 times until it is detected. phablet@ubuntu-phablet:~$ system-image-cli --info current build number: 129 device name: mako channel: ubuntu-touch/devel-proposed alias: ubuntu-touch/vivid-proposed last update: 2015-03-11 13:19:54 version version: 129 version ubuntu: 20150310.3 version device: 20150210 version custom: 20150310.3 To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1430769/+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 822479] Re: Massive Evolution Mail memory leak
I'm not sure if this is directly related but I notice a massive memory link with writing email with HTML content, such as pasted content from a webpage. This also applies to images that are inserted, as these create HTML containers around the images, thus causing a leak. The leak is apparent when pressing backspace after HTML content has been inserted. Typing is fast and responsive, but backspace takes one to two seconds to complete. It's often faster to highlight and delete than to press backspace. This leak causes sending of messages to freeze the window, causing it to grey out. As a final note, I've found that including a signature and attempting to delete it will crash Evolution instantly, although this may be an unrelated bug. Setup: Evolution 3.16 or 3.17 (needed latest development release to fix previous bugs) Exchange plugin Lenovo Yoga Pro 2 - 8GB Ram Ubuntu 15.04 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to evolution in Ubuntu. https://bugs.launchpad.net/bugs/822479 Title: Massive Evolution Mail memory leak Status in evolution package in Ubuntu: Confirmed Bug description: While there are lots of posts on Evolution memory leaks, this appears to be new. No Natty, evolution starts with around 60mb of usage, and climbs up. Over the past 90 minutes it reached 385mb. Finally killed it. Restarting goes back to the 60mb again. I ran it this time from the command line with: evolution --debug-file= Here is the contents of this file: -- (evolution:2239): GLib-GObject-CRITICAL **: Object class EMFolderTree doesn't implement property 'paste-target-list' from interface 'ESelectable' (evolution:2239): GLib-GObject-CRITICAL **: Object class EMFolderTree doesn't implement property 'copy-target-list' from interface 'ESelectable' (firefox-bin:8739): LIBDBUSMENU-GTK-CRITICAL **: dbusmenu_menuitem_property_set_shortcut: assertion `gtk_accelerator_valid(key, modifier)' failed ** (:9247): DEBUG: NP_Initialize ** (:9247): DEBUG: NP_Initialize succeeded ** (:9247): DEBUG: NP_Shutdown NOTE: child process received `Goodbye', closing down NOTE: child process received `Goodbye', closing down java version "1.6.0_22" OpenJDK Runtime Environment (IcedTea6 1.10.2) (6b22-1.10.2-0ubuntu1~11.04.1) OpenJDK Server VM (build 20.0-b11, mixed mode) (firefox-bin:8739): GLib-CRITICAL **: g_source_remove: assertion `tag > 0' failed (firefox-bin:8739): GLib-CRITICAL **: g_source_remove: assertion `tag > 0' failed No idea what's going on here. If I don't kill evolution regularly my ram gets eaten up and my system freezes. I have uninstalled evolution with the 'purge' option, and reinstalled. I then restored evolution from previously backed up settings, so it's possible there's some problem in my settings. But where? I have 4 imap+ accounts running, plus a pop service. There are about 60 emails in each account, with more archived in a local folder on my computer. I have about 5 local calendars, all measured in kb of data. Any thoughts as to what's going on? I'm aware that Ubuntu is ditching evolution for the next release, so need a work around until then. Cheers. ProblemType: Bug DistroRelease: Ubuntu 11.04 Package: evolution 2.32.2-0ubuntu7 ProcVersionSignature: Ubuntu 2.6.38-10.46-generic 2.6.38.7 Uname: Linux 2.6.38-10-generic i686 Architecture: i386 Date: Mon Aug 8 10:59:41 2011 EcryptfsInUse: Yes InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release i386 (20110427.1) ProcEnviron: LANGUAGE=en_AU:en PATH=(custom, user) LANG=en_AU.UTF-8 SHELL=/bin/bash SourcePackage: evolution UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evolution/+bug/822479/+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 1487129] Re: camera-app mic permission item blank
@mpt, lp:1487152 also relevant to two-perms schema. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1487129 Title: camera-app mic permission item blank Status in Canonical System Image: In Progress Status in pulseaudio package in Ubuntu: In Progress Status in ubuntu-system-settings package in Ubuntu: Invalid Bug description: Working through camera/mic trust issues, discovering that the camera- app's mic item under "Other app access" is blank, will attach a screenie. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1487129/+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 1471572] [NEW] Cintiq 13HD Touch support requires input-wacom >=0.28
Public bug reported: The Wacom Cintiq 13HD Touch support requires input-wacom >=0.28. I was wondering if a more recent version of xf86-input-wacom and libwacom could be introduced to take advantage of more device support and various bugfixes. Release notes of all versions: http://sourceforge.net/p/linuxwacom/mailman/linuxwacom-announce/ Some benefits listed below: 0.30: - xsetwacom mapping bugfix 0.28.0: - introduces the Cintiq 13HDT support that I am looking for - improved functionality and bugfixes for kernel 4.1 0.27.0: - support for Cintiq 27QHD, 27QHD Touch, Bamboo Pad ** Affects: xf86-input-wacom (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xf86-input-wacom in Ubuntu. https://bugs.launchpad.net/bugs/1471572 Title: Cintiq 13HD Touch support requires input-wacom >=0.28 Status in xf86-input-wacom package in Ubuntu: New Bug description: The Wacom Cintiq 13HD Touch support requires input-wacom >=0.28. I was wondering if a more recent version of xf86-input-wacom and libwacom could be introduced to take advantage of more device support and various bugfixes. Release notes of all versions: http://sourceforge.net/p/linuxwacom/mailman/linuxwacom-announce/ Some benefits listed below: 0.30: - xsetwacom mapping bugfix 0.28.0: - introduces the Cintiq 13HDT support that I am looking for - improved functionality and bugfixes for kernel 4.1 0.27.0: - support for Cintiq 27QHD, 27QHD Touch, Bamboo Pad To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xf86-input-wacom/+bug/1471572/+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 1469265] [NEW] package libreoffice-presentation-minimizer 1:4.2.8-0ubuntu2 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it befo
Public bug reported: Help me ProblemType: Package DistroRelease: Ubuntu 14.04 Package: libreoffice-presentation-minimizer 1:4.2.8-0ubuntu2 ProcVersionSignature: Ubuntu 3.13.0-55.94-generic 3.13.11-ckt20 Uname: Linux 3.13.0-55-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.11 Architecture: amd64 Date: Fri Jun 26 12:24:46 2015 DuplicateSignature: package:libreoffice-presentation-minimizer:1:4.2.8-0ubuntu2:package is in a very bad inconsistent state; you should reinstall it before attempting configuration ErrorMessage: package is in a very bad inconsistent state; you should reinstall it before attempting configuration InstallationDate: Installed on 2015-03-20 (98 days ago) InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2) PackageArchitecture: all SourcePackage: libreoffice Title: package libreoffice-presentation-minimizer 1:4.2.8-0ubuntu2 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: libreoffice (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package need-duplicate-check trusty -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libreoffice in Ubuntu. https://bugs.launchpad.net/bugs/1469265 Title: package libreoffice-presentation-minimizer 1:4.2.8-0ubuntu2 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration Status in libreoffice package in Ubuntu: New Bug description: Help me ProblemType: Package DistroRelease: Ubuntu 14.04 Package: libreoffice-presentation-minimizer 1:4.2.8-0ubuntu2 ProcVersionSignature: Ubuntu 3.13.0-55.94-generic 3.13.11-ckt20 Uname: Linux 3.13.0-55-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.11 Architecture: amd64 Date: Fri Jun 26 12:24:46 2015 DuplicateSignature: package:libreoffice-presentation-minimizer:1:4.2.8-0ubuntu2:package is in a very bad inconsistent state; you should reinstall it before attempting configuration ErrorMessage: package is in a very bad inconsistent state; you should reinstall it before attempting configuration InstallationDate: Installed on 2015-03-20 (98 days ago) InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2) PackageArchitecture: all SourcePackage: libreoffice Title: package libreoffice-presentation-minimizer 1:4.2.8-0ubuntu2 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1469265/+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 757814] Re: Static Application Switcher Plugin does not show window titles
This bug is not a duplicate of 838222 because this bug describes the CompizConfig Static Application Switcher plug-in, not the default Unity application switcher described in bug 838222. These are different pieces of code so they should have different bug reports. I am using Ubuntu 14.04 but using the Static Application Switcher instead of the Unity default application switcher because of other undesirable behaviour in the default switcher. I believe that proper attention to this bug was drawn away by declaring it a duplicate. I hope the developers of the Static Application Switcher are alerted to this bug as it continues to be an issue. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to compiz in Ubuntu. https://bugs.launchpad.net/bugs/757814 Title: Static Application Switcher Plugin does not show window titles Status in Ayatana Design: New Status in Unity: Incomplete Status in compiz package in Ubuntu: Confirmed Status in unity package in Ubuntu: Incomplete Bug description: When using Alt+Tab Static Switcher Plugin in Natty the pop-up notification does not show the window name. It also happens with "Exposé". I think (without testing) that it may affect other plugins that deal with windows and that in the past presented windows' names. To manage notifications about this bug go to: https://bugs.launchpad.net/ayatana-design/+bug/757814/+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 757814] Re: Static Application Switcher Plugin does not show window titles
** This bug is no longer a duplicate of bug 838222 Alt-tab - In the window spread, the currently selected window should display a title bar -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to unity in Ubuntu. Matching subscriptions: dp-unity https://bugs.launchpad.net/bugs/757814 Title: Static Application Switcher Plugin does not show window titles Status in Ayatana Design: New Status in Unity: Incomplete Status in compiz package in Ubuntu: Confirmed Status in unity package in Ubuntu: Incomplete Bug description: When using Alt+Tab Static Switcher Plugin in Natty the pop-up notification does not show the window name. It also happens with "Exposé". I think (without testing) that it may affect other plugins that deal with windows and that in the past presented windows' names. To manage notifications about this bug go to: https://bugs.launchpad.net/ayatana-design/+bug/757814/+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 1218322] Re: Can't set keyboard layout change to alt+shift, ctrl+shift, etc.
I can't type Esperanto. The option button that allows me turn on Esperanto Circumflexes is gone! Does Gnome project hates people that speaks Esperanto? -- 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/1218322 Title: Can't set keyboard layout change to alt+shift, ctrl+shift, etc. Status in Gnome Settings Daemon: Unknown Status in Ubuntu GNOME: Fix Released Status in gnome-control-center package in Ubuntu: Fix Released Status in gnome-settings-daemon package in Ubuntu: Triaged Status in gnome-settings-daemon source package in Saucy: Won't Fix Status in gnome-control-center package in ALT Linux: Unknown Status in gnome-control-center package in Baltix: Confirmed Status in gnome-control-center package in Gentoo Linux: Invalid Status in gnome-control-center package in Mandriva: Invalid Bug description: [Impact] Can't set keyboard layout change to Ctrl+Shift, Caps Lock, Alt+Shift, etc. Shift, Caps Lock keys are just ignored in settings. [Test Case] - open gnome-control-center's text input settings - click on the "next layout key" entry - try entering a combination of two modifier keys such as Ctrl+Shift -> the UI should reflect the new keys - add at least two input sources through gnome-control-center's text entry settings - press and release Ctrl+Shift -> the current input source should change [Regression Potential] That UI was not working before, it should only be an improvement (some key combos are not working as expected, that's another issue and shouldn't be mixed with this one) The input switching shortcut might capture other non-modifier shortcuts, but users will need to consider this when choosing their switching shortcut anyways. For users this bug affects, this represents a working solution for a critical bug. -- Test results for different keyboard layout change hotkeys may be viewed and added in the Google Docs table, created by Norbert (https://docs.google.com/spreadsheet/ccc?key=0Ao5e713Ig9g_dEJrX2NRYlpLWWVzSWxsVXU4ck9HYVE&usp=sharing). You can use the tag keyboard-layout-switching-hotkeys to find related bugs. https://bugs.launchpad.net/ubuntu/+bugs?field.tag=keyboard-layout-switching-hotkeys For using layout switching hotkeys in Unity Greeter, see bug 1245137. For using layout switching hotkeys in GNOME lockscreen, see bug 1244548. -- ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: indicator-keyboard 0.0.0+13.10.20130829.1-0ubuntu1 ProcVersionSignature: Ubuntu 3.11.0-2.5-generic 3.11.0-rc5 Uname: Linux 3.11.0-2-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.12.1-0ubuntu2 Architecture: amd64 Date: Thu Aug 29 14:21:54 2013 InstallationDate: Installed on 2013-07-31 (28 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Alpha amd64 (20130730) MarkForUpload: True ProcEnviron: LANGUAGE=ru_UA:ru PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=ru_UA.UTF-8 SHELL=/bin/bash SourcePackage: indicator-keyboard UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-settings-daemon/+bug/1218322/+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 1441193] [NEW] Login screen crashes after HDMI cable is plugged in, resumed from suspend
Public bug reported: I have a laptop that I connect to an external monitor. After I open the lid and hit a button to wake the computer I will connect the HDMI cable for the monitor. After plugging in the HDMI, the login screen freezes intermittently so I can't type in my password. The mouse is missing and unresponsive and the keyboard doesn't type anything. To fix this I press Ctrl-Alt-F1 and log into the terminal. I then use the command "sudo service lightdm restart" to restart the window manager. This fixes the login issue, however it also closes all of the open applications that I had on suspend, which is not desirable. Sometimes, after typing in my password once I've restarted lightdm, the display will get locked into a weird "refresh" state, where the user session doesn't start and the screen is stuck with no window manager, no dash, and the background is partially on both screens. If the computer gets into this weird display mode then the only fix is to reboot. I would like to be able to plug in the HDMI from a sleep and be assured that the computer can recover the running session without crashing the login screen or the display manager. Repro steps: - Close laptop lid to put it to sleep - Connect HDMI cable - Open lid and press button (optionally, open lid then connect cable) Graphics: - Intel HD 4000 Computer: - Lenovo Yoga Pro 2 ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: lightdm 1.12.3-0ubuntu1 ProcVersionSignature: Ubuntu 3.16.0-34.45-generic 3.16.7-ckt8 Uname: Linux 3.16.0-34-generic x86_64 ApportVersion: 2.14.7-0ubuntu8.2 Architecture: amd64 CurrentDesktop: Unity Date: Tue Apr 7 07:14:29 2015 EcryptfsInUse: Yes InstallationDate: Installed on 2014-12-18 (110 days ago) InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1) SourcePackage: lightdm UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: lightdm (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug utopic -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1441193 Title: Login screen crashes after HDMI cable is plugged in, resumed from suspend Status in lightdm package in Ubuntu: New Bug description: I have a laptop that I connect to an external monitor. After I open the lid and hit a button to wake the computer I will connect the HDMI cable for the monitor. After plugging in the HDMI, the login screen freezes intermittently so I can't type in my password. The mouse is missing and unresponsive and the keyboard doesn't type anything. To fix this I press Ctrl-Alt-F1 and log into the terminal. I then use the command "sudo service lightdm restart" to restart the window manager. This fixes the login issue, however it also closes all of the open applications that I had on suspend, which is not desirable. Sometimes, after typing in my password once I've restarted lightdm, the display will get locked into a weird "refresh" state, where the user session doesn't start and the screen is stuck with no window manager, no dash, and the background is partially on both screens. If the computer gets into this weird display mode then the only fix is to reboot. I would like to be able to plug in the HDMI from a sleep and be assured that the computer can recover the running session without crashing the login screen or the display manager. Repro steps: - Close laptop lid to put it to sleep - Connect HDMI cable - Open lid and press button (optionally, open lid then connect cable) Graphics: - Intel HD 4000 Computer: - Lenovo Yoga Pro 2 ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: lightdm 1.12.3-0ubuntu1 ProcVersionSignature: Ubuntu 3.16.0-34.45-generic 3.16.7-ckt8 Uname: Linux 3.16.0-34-generic x86_64 ApportVersion: 2.14.7-0ubuntu8.2 Architecture: amd64 CurrentDesktop: Unity Date: Tue Apr 7 07:14:29 2015 EcryptfsInUse: Yes InstallationDate: Installed on 2014-12-18 (110 days ago) InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1) SourcePackage: lightdm UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1441193/+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 1376760] Re: after a screen rotation we get a double mouse pointer
This bug still affects me. 14.10 x64 Yoga Pro 2. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-video-intel in Ubuntu. https://bugs.launchpad.net/bugs/1376760 Title: after a screen rotation we get a double mouse pointer Status in X.org xf86-video-intel: Fix Released Status in xserver-xorg-video-intel package in Ubuntu: Confirmed Bug description: On ubuntu version 14.10 after a screen rotation when we come back to normal rotation our mouse pointer is doubled: the old rotated one and the actual one. This bug was already reported in: https://bugs.freedesktop.org/show_bug.cgi?id=81886 with a complete solution. I checked that code compiled for 14.10 does not contain the fix in file: src/sna/sna_display.c ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: xserver-xorg-video-intel 2:2.99.914-1~exp1ubuntu3 Uname: Linux 3.17.0-031700rc7-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.14.7-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 CurrentDesktop: Unity Date: Thu Oct 2 16:35:59 2014 DistUpgraded: 2014-09-23 12:09:08,269 DEBUG disabling apt cron job (0o755) DistroCodename: utopic DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Lenovo Device [17aa:3977] InstallationDate: Installed on 2013-11-14 (322 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) MachineType: LENOVO 2191 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.17.0-031700rc7-generic root=UUID=42f32e25-c311-4811-9c71-19fd8ef53c6d ro quiet acpi_backlight=vendor SourcePackage: xserver-xorg-video-intel UpgradeStatus: Upgraded to utopic on 2014-09-23 (9 days ago) dmi.bios.date: 01/21/2013 dmi.bios.vendor: LENOVO dmi.bios.version: 66CN54WW dmi.board.asset.tag: No Asset Tag dmi.board.name: INVALID dmi.board.vendor: LENOVO dmi.board.version: 3193WIN8 STD MLT dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo IdeaPad Yoga 13 dmi.modalias: dmi:bvnLENOVO:bvr66CN54WW:bd01/21/2013:svnLENOVO:pn2191:pvrLenovoIdeaPadYoga13:rvnLENOVO:rnINVALID:rvr3193WIN8STDMLT:cvnLENOVO:ct10:cvrLenovoIdeaPadYoga13: dmi.product.name: 2191 dmi.product.version: Lenovo IdeaPad Yoga 13 dmi.sys.vendor: LENOVO version.compiz: compiz 1:0.9.12+14.10.20140918-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.56-1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.3.0-0ubuntu2 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.3.0-0ubuntu2 version.xserver-xorg-core: xserver-xorg-core 2:1.16.0-1ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.0-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.4.0-2ubuntu2 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.914-1~exp1ubuntu3 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.11-1ubuntu2 xserver.bootTime: Thu Oct 2 12:37:20 2014 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id 864 vendor LGD xserver.version: 2:1.16.0-1ubuntu1 To manage notifications about this bug go to: https://bugs.launchpad.net/xserver-xorg-video-intel/+bug/1376760/+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 1410124] [NEW] nvidia-331 331.113-0ubuntu0.0.4: nvidia-331 kernel module failed to build
Public bug reported: Install failed ProblemType: Package DistroRelease: Ubuntu 14.04 Package: nvidia-331 331.113-0ubuntu0.0.4 ProcVersionSignature: Ubuntu 3.13.0-43.72-generic 3.13.11.11 Uname: Linux 3.13.0-43-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.14.1-0ubuntu3.6 Architecture: amd64 DKMSKernelVersion: 3.13.0-44-generic Date: Tue Jan 13 09:28:03 2015 InstallationDate: Installed on 2014-08-08 (158 days ago) InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2) PackageVersion: 331.113-0ubuntu0.0.4 SourcePackage: nvidia-graphics-drivers-331 Title: nvidia-331 331.113-0ubuntu0.0.4: nvidia-331 kernel module failed to build UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: nvidia-graphics-drivers-331 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package trusty -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-graphics-drivers-331 in Ubuntu. https://bugs.launchpad.net/bugs/1410124 Title: nvidia-331 331.113-0ubuntu0.0.4: nvidia-331 kernel module failed to build Status in nvidia-graphics-drivers-331 package in Ubuntu: New Bug description: Install failed ProblemType: Package DistroRelease: Ubuntu 14.04 Package: nvidia-331 331.113-0ubuntu0.0.4 ProcVersionSignature: Ubuntu 3.13.0-43.72-generic 3.13.11.11 Uname: Linux 3.13.0-43-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.14.1-0ubuntu3.6 Architecture: amd64 DKMSKernelVersion: 3.13.0-44-generic Date: Tue Jan 13 09:28:03 2015 InstallationDate: Installed on 2014-08-08 (158 days ago) InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2) PackageVersion: 331.113-0ubuntu0.0.4 SourcePackage: nvidia-graphics-drivers-331 Title: nvidia-331 331.113-0ubuntu0.0.4: nvidia-331 kernel module failed to build 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-331/+bug/1410124/+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 1323736] Re: Segmentation Fault when Opening Appearance
Same problem. First error: (unity-control-center:20928): unity-control-center-WARNING **: Could not load /usr/share/themes/Adwaita/index.theme: No such file or directory Segmentation fault (core dumped) After installing gnome-themes-standard: (unity-control-center:21272): Gtk-CRITICAL **: gtk_radio_button_set_group: assertion '!g_slist_find (group, radio_button)' failed Segmentation fault (core dumped) Ubuntu 14.04 upgraded from 13.10, x64, NVidia graphics. Considering re- installing 14.04 if Appearance works in live CD. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to unity-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1323736 Title: Segmentation Fault when Opening Appearance Status in “unity-control-center” package in Ubuntu: Confirmed Bug description: When I open unity-control-center and click on Appearance, most of the time it crashes as soon as it finishes loading the wallpaper thumbnails. Sometimes, the command-line output is as follows: - (unity-control-center:4394): Gtk-CRITICAL **: gtk_radio_button_set_group: assertion '!g_slist_find (group, radio_button)' failed (unity-control-center:4394): Gtk-CRITICAL **: gtk_radio_button_set_group: assertion '!g_slist_find (group, radio_button)' failed (unity-control-center:4394): Gtk-CRITICAL **: gtk_radio_button_set_group: assertion '!g_slist_find (group, radio_button)' failed (unity-control-center:4394): unity-control-center-WARNING **: Could not load /usr/share/themes/Adwaita/index.theme: No such file or directory (unity-control-center:4394): GLib-GObject-CRITICAL **: g_object_unref: assertion 'G_IS_OBJECT (object)' failed *** BUG *** In pixman_region32_init_rect: Invalid rectangle passed Set a breakpoint on '_pixman_log_error' to debug Segmentation fault (core dumped) - And sometimes it looks like this (note the corruption error at the end): - (unity-control-center:4454): Gtk-CRITICAL **: gtk_radio_button_set_group: assertion '!g_slist_find (group, radio_button)' failed (unity-control-center:4454): Gtk-CRITICAL **: gtk_radio_button_set_group: assertion '!g_slist_find (group, radio_button)' failed (unity-control-center:4454): Gtk-CRITICAL **: gtk_radio_button_set_group: assertion '!g_slist_find (group, radio_button)' failed (unity-control-center:4454): unity-control-center-WARNING **: Could not load /usr/share/themes/Adwaita/index.theme: No such file or directory (unity-control-center:4454): GLib-GObject-CRITICAL **: g_object_unref: assertion 'G_IS_OBJECT (object)' failed *** BUG *** In pixman_region32_init_rect: Invalid rectangle passed Set a breakpoint on '_pixman_log_error' to debug *** Error in `unity-control-center': double free or corruption (!prev): 0x7fe5fc0dfb40 *** Aborted (core dumped) Running Ubuntu 14.04, unity-control-center 14.04.3+14.04.20140410-0ubuntu1. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity-control-center/+bug/1323736/+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 1358190] [NEW] archive manager is not warning when corrupt tar opened
Public bug reported: I have occasionally experienced instances when my backups using tar have created a bad .tar file. Archive Manager opens the archive file and the archive hierarchy is partially displayed, but there is no warning that file is corrupt and the displayed tree is corrupt/incomplete. Listing archive with tar -t exits with error, and opening the archive with an alternative manager (ark) also displays partial hierarchy, but does display a message warning that the tar file is corrupt. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: file-roller 3.10.2.1-0ubuntu4.1 ProcVersionSignature: Ubuntu 3.13.0-34.60-generic 3.13.11.4 Uname: Linux 3.13.0-34-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.3 Architecture: amd64 CurrentDesktop: Unity Date: Mon Aug 18 09:40:14 2014 InstallationDate: Installed on 2011-11-01 (1020 days ago) InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012) SourcePackage: file-roller UpgradeStatus: Upgraded to trusty on 2014-04-18 (121 days ago) ** Affects: file-roller (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug trusty -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to file-roller in Ubuntu. https://bugs.launchpad.net/bugs/1358190 Title: archive manager is not warning when corrupt tar opened Status in “file-roller” package in Ubuntu: New Bug description: I have occasionally experienced instances when my backups using tar have created a bad .tar file. Archive Manager opens the archive file and the archive hierarchy is partially displayed, but there is no warning that file is corrupt and the displayed tree is corrupt/incomplete. Listing archive with tar -t exits with error, and opening the archive with an alternative manager (ark) also displays partial hierarchy, but does display a message warning that the tar file is corrupt. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: file-roller 3.10.2.1-0ubuntu4.1 ProcVersionSignature: Ubuntu 3.13.0-34.60-generic 3.13.11.4 Uname: Linux 3.13.0-34-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.3 Architecture: amd64 CurrentDesktop: Unity Date: Mon Aug 18 09:40:14 2014 InstallationDate: Installed on 2011-11-01 (1020 days ago) InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012) SourcePackage: file-roller UpgradeStatus: Upgraded to trusty on 2014-04-18 (121 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/file-roller/+bug/1358190/+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 1238137] Re: Maguro: Network Manager is not reconnecting ofono's gprs connection after a cellular turn off
** Tags added: qa-daily-testing rtm14 -- 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/1238137 Title: Maguro: Network Manager is not reconnecting ofono's gprs connection after a cellular turn off Status in “network-manager” package in Ubuntu: Triaged Bug description: Steps: 1. Flash the phone with image 91 2. Open a web browser 3. Open System settings 4. Click on cellular 5. Disconnect 6. Leave till the screen blanks 7. Unlock the phone 8. Reconnect the cellular 9. Refresh the browser. davmor2@boromir:~$ adb shell /usr/share/ofono/scripts/list-modems [ /ril_0 ] Features = sms net gprs sim Emergency = 0 Powered = 1 Lockdown = 0 Interfaces = org.ofono.CallVolume org.ofono.MessageManager org.ofono.NetworkRegistration org.ofono.ConnectionManager org.ofono.NetworkTime org.ofono.VoiceCallManager org.ofono.SimManager Online = 1 Model = Fake Modem Model Revision = I9250XXLJ1 Type = hardware Serial = 351554052322998 Manufacturer = Fake Manufacturer [ org.ofono.CallVolume ] Muted = 1 SpeakerVolume = 0 MicrophoneVolume = 0 [ org.ofono.MessageManager ] [ org.ofono.NetworkRegistration ] Status = registered Strength = 16 Name = T-Mobile Orange LocationAreaCode = 3218 Mode = auto MobileCountryCode = 234 Technology = umts CellId = 210924067 MobileNetworkCode = 33 [ org.ofono.ConnectionManager ] Attached = 1 RoamingAllowed = 0 Suspended = 0 Powered = 1 [ org.ofono.NetworkTime ] [ org.ofono.VoiceCallManager ] EmergencyNumbers = 112 999 911 [ org.ofono.SimManager ] Retries = MobileCountryCode = 234 FixedDialing = 0 SubscriberNumbers = 07572378845 PreferredLanguages = en BarredDialing = 0 CardIdentifier = 8944302031557237537 LockedPins = MobileNetworkCode = 30 SubscriberIdentity = 234308342877614 Present = 1 PinRequired = none davmor2@boromir:~$ adb shell /usr/share/ofono/scripts/list-contexts [ /ril_0 ] [ /ril_0/context1 ] Username = User Protocol = ip Name = Internet Settings = { } IPv6.Settings = { } Active = 0 AccessPointName = general.t-mobile.uk Password = mms Type = internet To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1238137/+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 1231964] Re: NetworkManager crashes in ofono plugin with phonesim [crashed with SIGSEGV in in ??()]
Not marking qa-daily-testing as doesn't appear user-facing. -- 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/1231964 Title: NetworkManager crashes in ofono plugin with phonesim [crashed with SIGSEGV in in ??()] Status in “network-manager” package in Ubuntu: Triaged Bug description: When I run ofono-phonesim on the G4 (mako), NetworkManager goes into an eternal crash/restart loop with this crash. After "sudo stop network-manager" and running it manually with "sudo /usr/sbin/NetworkManager --no-daemon" I see: NetworkManager[31290]: /sys/devices/virtual/net/sit0: couldn't determine device driver; ignoring... NetworkManager[31290]: (/phonesim): failed to look up interface index NetworkManager[31290]: (/phonesim): new Ofono device (driver: 'ofono' ifindex: 0) NetworkManager[31290]: (/phonesim): exported as /org/freedesktop/NetworkManager/Devices/1 NetworkManager[31290]: (/phonesim): device state change: unmanaged -> unavailable (reason 'managed') [10 20 2] NetworkManager[31290]: (/phonesim): deactivating device (reason 'managed') [2] NetworkManager[31290]: (/phonesim) updated available interfaces NetworkManager[31290]: WWAN now enabled by management service NetworkManager[31290]: (/phonesim) marked enabled: 1 NetworkManager[31290]:SCPlugin-Ofono: reading configuration for IMSI 246813579 NetworkManager[31290]:SCPlugin-Ofono: add context for 246813579 NetworkManager[31290]:SCPlugin-Ofono: add property 'Name': Internet NetworkManager[31290]:SCPlugin-Ofono: add property 'AccessPointName': NetworkManager[31290]:SCPlugin-Ofono: add property 'Username': NetworkManager[31290]:SCPlugin-Ofono: add property 'Password': NetworkManager[31290]:SCPlugin-Ofono: add property 'Type': internet NetworkManager[31290]:SCPlugin-Ofono: add property 'Protocol': ip NetworkManager[31290]:SCPlugin-Ofono: found internet context 'Internet' (context1) NetworkManager[31290]: (wlan0) supports 5 scan SSIDs NetworkManager[31290]: Trying to remove a non-existant call id. NetworkManager[31290]: (wlan0): supplicant interface state: starting -> ready NetworkManager[31290]: (wlan0): device state change: unavailable -> disconnected (reason 'supplicant-available') [20 30 42] NetworkManager[31290]: (/phonesim): device state change: unavailable -> disconnected (reason 'none') [20 30 0] NetworkManager[31290]: Auto-activating connection '/262026260068068/context1'. NetworkManager[31290]: Activation (/phonesim) starting connection '/262026260068068/context1' NetworkManager[31290]: (/phonesim): device state change: disconnected -> prepare (reason 'none') [30 40 0] NetworkManager[31290]: Activation (/phonesim) Stage 1 of 5 (Device Prepare) scheduled... NetworkManager[31290]: Activation (/phonesim) Stage 1 of 5 (Device Prepare) started... NetworkManager[31290]: Activation (/phonesim) Stage 1 of 5 (Device Prepare) complete. NetworkManager[31290]: (wlan0): supplicant interface state: ready -> inactive NetworkManager[31290]: (wlan0) supports 5 scan SSIDs NetworkManager[31290]: Activation (/phonesim) Stage 2 of 5 (Device Configure) scheduled... NetworkManager[31290]: Activation (/phonesim) Stage 2 of 5 (Device Configure) starting... NetworkManager[31290]: (/phonesim): device state change: prepare -> config (reason 'none') [40 50 0] NetworkManager[31290]: Activation (/phonesim) Stage 2 of 5 (Device Configure) successful. NetworkManager[31290]: Activation (/phonesim) Stage 3 of 5 (IP Configure Start) scheduled. NetworkManager[31290]: Activation (/phonesim) Stage 2 of 5 (Device Configure) complete. NetworkManager[31290]: Activation (/phonesim) Stage 3 of 5 (IP Configure Start) started... NetworkManager[31290]: (/phonesim): device state change: config -> ip-config (reason 'none') [50 70 0] NetworkManager[31290]: Activation (/phonesim) Stage 4 of 5 (IPv6 Configure Timeout) scheduled... NetworkManager[31290]: Activation (/phonesim) Stage 3 of 5 (IP Configure Start) complete. NetworkManager[31290]: (/phonesim): IPv4 static configuration: (NetworkManager:31290): GLib-GObject-CRITICAL **: g_value_get_string: assertion 'G_VALUE_HOLDS_STRING (value)' failed Reproducer: - Take current phone build and put it into write mode - Install ofono-phonesim xvfb-run - Edit /etc/ofono/phonesim.conf and enable the commented out phonesim stanza - sudo stop ofono - In ssh/terminal 1, start ofono (in the foreground): sudo ofonod -P ril -n - In ssh/terminal 2: * start the simulator: xvfb-run -a ofono-phonesim -p 12345 /usr/share/phonesim/default.xml & * start the modem: /usr/share/ofono/scripts/enable-modem * run NM: sudo /usr/sbin/NetworkManager --no-daemon This reproduces the crash. ProblemType: Crash DistroRelease: Ubuntu 13.10
[Desktop-packages] [Bug 1322181] Re: file-roller isn't properly opening some rar files
As mentioned in my bug report which was marked duplicate... https://bugs.launchpad.net/linuxmint/+bug/1333420 There is a fix for the problem (in this thread): http://forums.linuxmint.com/viewtopic.php?f=90&t=168934&p=879933#p879933 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to file-roller in Ubuntu. https://bugs.launchpad.net/bugs/1322181 Title: file-roller isn't properly opening some rar files Status in “file-roller” package in Ubuntu: Confirmed Bug description: Mint 17 RC Qiana x64 default kernel 3.13.0-24 after downloading a zip file with subtitles inside it (*.srt PT-pt), when i opening it on file-roller, check screen to what happens: http://i.imgur.com/jP8A4hC.png has you see the windows on the right are two subtitle files. name of the srt type subtitle, inside the zip file is un-properlly formated, and its open has read-only. window on the right is a "normal" compressed file, so you can check how it should look like. here you have download for a zip with PT-pt subtitles: https://www.dropbox.com/s/g0potr9u9t7i264/Hannibal.2013-www.LegendasDivx.com_37.rar for testing. if you guys need more information, please dont hesitate in contact me. regards, and keep up the awesome job on Mint :) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/file-roller/+bug/1322181/+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 792085] Re: Automatic remount of safely removed drive
I have this problem as well with 14.04. The eject button in Nautilus works as I can see the device unmount from /media/username/DeviceName, then it immediately remounts. There are no errors with using "sudo umount /media/username/DeviceName", however the device will also remount. I've also gotten the error "Cannot eject drive in use: Device /dev/sdg1 is mounted" until I close all Nautilus windows and reopen one, but this may not be related. Device specs: - USB 64G (PNY) - Fat32 format - 1 Primary partition - Bootable - Created with Startup Disk Creator -- 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/792085 Title: Automatic remount of safely removed drive Status in “nautilus” package in Ubuntu: Confirmed Status in “udev” package in Ubuntu: Confirmed Bug description: Binary package hint: nautilus When I choose "Safely remove drive" context menu entry for an external USB drive within a nautilus window or directly clicking on the desktop icon, after about 10 seconds the drive is automatically remounted and a Nautilus window showing the root folder opens. I have noticed that similar already happened with a very old Ubuntu version - Bug #110589 and as that is so long time ago I thought it is better to open a new bug. Reason of the problem might even be completely different. ProblemType: Bug DistroRelease: Ubuntu 11.04 Package: nautilus 1:2.32.2.1-0ubuntu13 ProcVersionSignature: Ubuntu 2.6.38-8.42-generic-pae 2.6.38.2 Uname: Linux 2.6.38-8-generic-pae i686 Architecture: i386 Date: Thu Jun 2 23:40:08 2011 InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release i386 (20110427.1) ProcEnviron: LANGUAGE=en_US:en LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/792085/+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 1297421] Re: Sound stops working occasionally on Latitude E7440
I've been suffering with this problem too, though I've also been suffering with it in 13.10. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1297421 Title: Sound stops working occasionally on Latitude E7440 Status in “pulseaudio” package in Ubuntu: Confirmed Bug description: Sound stops(and starts) working from time to time with no definitive cause, it usually doesn't happen while something is playing so this makes it harder to find the cause. It happened once after resume from suspend(STR), restarting fixed it. Another time it happened after unplugging the AC adapter and turning on the hardware WiFi button, suspending to RAM and resuming fixed it. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: ubuntu-release-upgrader-core 1:0.219 ProcVersionSignature: Ubuntu 3.13.0-19.40-generic 3.13.6 Uname: Linux 3.13.0-19-generic x86_64 ApportVersion: 2.13.3-0ubuntu1 Architecture: amd64 CrashDB: ubuntu CurrentDesktop: KDE Date: Tue Mar 25 19:23:29 2014 InstallationDate: Installed on 2014-03-18 (6 days ago) InstallationMedia: Kubuntu 14.04 LTS "Trusty Tahr" - Alpha amd64 (20140227) PackageArchitecture: all SourcePackage: ubuntu-release-upgrader Symptom: dist-upgrade UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1297421/+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 1275908] Re: pkexec crashed with SIGABRT in g_assertion_message()
Ahah! Yes that helped a lot. :) http://askubuntu.com/questions/79987/how-to-re-install-software-center as did this one. I tried to download Tor, WordPress. I found out not necessarily a place for noobs. WordPress can't be configured "directly" on Ubuntu. It needs to be re-routed through a place like Juju. Which I am learning is also not for non-coders, and rookies to uploading and downloading files properly. I bought a WordPress Theme and wanted to launch it. Figured it come preconfigured where I go in write away. Not the case at all. Thanks for your help Seth. :) On 11 February 2014 01:45, Seth Arnold <1275...@bugs.launchpad.net> wrote: > Ah, very helpful. Your /etc/apt/sources.list.d/upubuntu-com- > tor64-saucy.list file is completely wrong, just delete it: > > sudo rm /etc/apt/sources.list.d/upubuntu-com-tor64-saucy.list > sudo apt-get update > > I don't know what you intended to have in that file, but there is > nothing there to salvage. So you might as well be rid of it. > > Thanks > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1275908 > > Title: > pkexec crashed with SIGABRT in g_assertion_message() > > Status in "policykit-1" package in Ubuntu: > Invalid > > Bug description: > No more info to offer. > > ProblemType: Crash > DistroRelease: Ubuntu 14.04 > Package: policykit-1 0.105-4ubuntu1 > ProcVersionSignature: Ubuntu 3.13.0-6.23-generic 3.13.0 > Uname: Linux 3.13.0-6-generic i686 > ApportVersion: 2.13.2-0ubuntu2 > Architecture: i386 > CrashCounter: 1 > CurrentDesktop: Unity > Date: Mon Feb 3 14:17:47 2014 > ExecutablePath: /usr/bin/pkexec > InstallationDate: Installed on 2014-01-11 (23 days ago) > InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release i386 > (20130424) > ProcAttrCurrent: /usr/lib/lightdm/lightdm-guest-session (enforce) > ProcCmdline: pkexec /usr/lib/gnome-settings-daemon/gsd-backlight-helper > --set-brightness 3 > ProcEnviron: >PATH=(custom, no user) >LANGUAGE=en_CA:en >XDG_RUNTIME_DIR= >LANG=en_CA.UTF-8 >SHELL=/bin/bash > Signal: 6 > SourcePackage: policykit-1 > StacktraceTop: >g_assertion_message () from /lib/i386-linux-gnu/libglib-2.0.so.0 >g_assertion_message_expr () from /lib/i386-linux-gnu/libglib-2.0.so.0 >?? () >__libc_start_main (main=0x80497f0, argc=4, argv=0xbf9de964, > init=0x804b0a0, fini=0x804b110, rtld_fini=0xb776c0f0 <_dl_fini>, > stack_end=0xbf9de95c) at libc-start.c:287 >?? () > Title: pkexec crashed with SIGABRT in g_assertion_message() > UpgradeStatus: Upgraded to trusty on 2014-01-18 (16 days ago) > UserGroups: > > To manage notifications about this bug go to: > > https://bugs.launchpad.net/ubuntu/+source/policykit-1/+bug/1275908/+subscriptions > -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to policykit-1 in Ubuntu. https://bugs.launchpad.net/bugs/1275908 Title: pkexec crashed with SIGABRT in g_assertion_message() Status in “policykit-1” package in Ubuntu: Invalid Bug description: No more info to offer. ProblemType: Crash DistroRelease: Ubuntu 14.04 Package: policykit-1 0.105-4ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-6.23-generic 3.13.0 Uname: Linux 3.13.0-6-generic i686 ApportVersion: 2.13.2-0ubuntu2 Architecture: i386 CrashCounter: 1 CurrentDesktop: Unity Date: Mon Feb 3 14:17:47 2014 ExecutablePath: /usr/bin/pkexec InstallationDate: Installed on 2014-01-11 (23 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release i386 (20130424) ProcAttrCurrent: /usr/lib/lightdm/lightdm-guest-session (enforce) ProcCmdline: pkexec /usr/lib/gnome-settings-daemon/gsd-backlight-helper --set-brightness 3 ProcEnviron: PATH=(custom, no user) LANGUAGE=en_CA:en XDG_RUNTIME_DIR= LANG=en_CA.UTF-8 SHELL=/bin/bash Signal: 6 SourcePackage: policykit-1 StacktraceTop: g_assertion_message () from /lib/i386-linux-gnu/libglib-2.0.so.0 g_assertion_message_expr () from /lib/i386-linux-gnu/libglib-2.0.so.0 ?? () __libc_start_main (main=0x80497f0, argc=4, argv=0xbf9de964, init=0x804b0a0, fini=0x804b110, rtld_fini=0xb776c0f0 <_dl_fini>, stack_end=0xbf9de95c) at libc-start.c:287 ?? () Title: pkexec crashed with SIGABRT in g_assertion_message() UpgradeStatus: Upgraded to trusty on 2014-01-18 (16 days ago) UserGroups: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/policykit-1/+bug/1275908/+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 1275908] Re: pkexec crashed with SIGABRT in g_assertion_message()
Ran: LANG=C;sudo apt-get --fix-missing install Reading package lists... Done Building dependency tree Reading state information... Done 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. videotron@videotron-Lenovo-B575:~$ LANG=C;sudo apt-get update -o APT::Cache-Limit=1 && sudo apt-get dist-upgrade E: Type 'gksudo' is not known on line 1 in source list /etc/apt/sources.list.d/upubuntu-com-tor64-saucy.list E: The list of sources could not be read. videotron@videotron-Lenovo-B575:~$ find /etc/apt -name '*.list' -exec bash -c 'echo -e "\n$1\n"; cat -n "$1"' _ '{}' \; /etc/apt/sources.list.d/upubuntu-com-tor32-saucy.list 1 deb-src http://ppa.launchpad.net/upubuntu-com/tor32/ubuntu raring main /etc/apt/sources.list.d/upubuntu-com-tor-trusty.list 1 deb http://ppa.launchpad.net/upubuntu-com/tor/ubuntu trusty main 2 # deb-src http://ppa.launchpad.net/upubuntu-com/tor/ubuntu trusty main 3 # deb-src http://ppa.launchpad.net/upubuntu-com/tor/ubuntu trusty main /etc/apt/sources.list.d/webupd8team-tor-browser-trusty.list 1 # deb http://ppa.launchpad.net/webupd8team/tor-browser/ubuntu trusty main 2 # deb-src http://ppa.launchpad.net/webupd8team/tor-browser/ubuntutrusty main 3 # deb-src http://ppa.launchpad.net/webupd8team/tor-browser/ubuntutrusty main /etc/apt/sources.list.d/ubuntu-wine-ppa-trusty.list 1 deb http://ppa.launchpad.net/ubuntu-wine/ppa/ubuntu trusty main 2 deb-src http://ppa.launchpad.net/ubuntu-wine/ppa/ubuntu trusty main /etc/apt/sources.list.d/upubuntu-com-tor64-trusty.list 1 # deb http://ppa.launchpad.net/upubuntu-com/tor64/ubuntu trusty main 2 # deb-src http://ppa.launchpad.net/upubuntu-com/tor64/ubuntu trusty main 3 # deb-src http://ppa.launchpad.net/upubuntu-com/tor64/ubuntu trusty main /etc/apt/sources.list.d/joe-yasi-yasi-trusty.list 1 deb http://ppa.launchpad.net/joe-yasi/yasi/ubuntu trusty main 2 deb-src http://ppa.launchpad.net/joe-yasi/yasi/ubuntu trusty main /etc/apt/sources.list.d/git-core-ppa-trusty.list 1 deb http://ppa.launchpad.net/git-core/ppa/ubuntu trusty main 2 deb-src http://ppa.launchpad.net/git-core/ppa/ubuntu trusty main /etc/apt/sources.list.d/yannubuntu-boot-repair-trusty.list 1 deb http://ppa.launchpad.net/yannubuntu/boot-repair/ubuntu trusty main 2 deb-src http://ppa.launchpad.net/yannubuntu/boot-repair/ubuntutrusty main 3 deb-src http://ppa.launchpad.net/yannubuntu/boot-repair/ubuntutrusty main /etc/apt/sources.list.d/google-talkplugin.list 1 ### THIS FILE IS AUTOMATICALLY CONFIGURED ### 2 # You may comment out this entry, but any other modifications may be lost. 3 # deb http://dl.google.com/linux/talkplugin/deb/ stable main /etc/apt/sources.list.d/upubuntu-com-tor64-saucy.list 1 gksudo apt-get update 2 gksudo get-apt install tor-browser 3 /etc/apt/sources.list 1 deb http://ca.archive.ubuntu.com/ubuntu/ trusty main universe restricted multiverse On 10 February 2014 23:48, John Lozinska wrote: > Or not :( Looked promising for a minute. Did remove the header issue > though I think. > > > On 10 February 2014 23:47, John Lozinska wrote: > >> looks like a hit! >> >> LANG=C;sudo apt-get --purge autoremove >> >> https://help.ubuntu.com/community/PackageManagerTroubleshootingProcedure >> >> >> >> On 10 February 2014 23:33, John Lozinska wrote: >> >>> ran: ubuntu-support-status >>> >>> Traceback (most recent call last): >>> File "/usr/bin/ubuntu-support-status", line 120, in >>> with apt.Cache() as cache: >>> File "/usr/lib/python3/dist-packages/apt/cache.py", line 103, in >>> __init__ >>> self.open(progress) >>> File "/usr/lib/python3/dist-packages/apt/cache.py", line 152, in open >>> self._list.read_main_list() >>> >>> >>> >>> On 10 February 2014 23:27, John Lozinska wrote: >>> Hope this helps E: The list of sources could not be read. Go to the repository dialog to correct the problem. E: _cache->open() failed, please report. On 10 February 2014 22:48, John Lozinska wrote: > bash: /etc/apt/sources.list: Permission denied > > > On 10 February 2014 22:36, John Lozinska wrote: > >> Also...can't load my disk drive. >> >> >> >> >> On 10 February 2014 22:33, John Lozinska wrote: >> >>> I don't code and obviously as you can see terrible at uploading and >>> writing files. It's essential I am noticing from my new experiences with >>> Ubuntu. Possible to write that in 'Ubuntu for dumbies' with step by step >>> directions? Sorry, but what you just said made little sense to me as to >>> where to even start. I also notice these questions instantly optimise to >>> Google search...which can be good and bad, depending on what files you >>> are >>> sharing. Also unsure of, as in the sense of hacking. @noobie >>> >>> >>> On 10 February 2014 18:04, Seth Arnol
Re: [Desktop-packages] [Bug 1275908] Re: pkexec crashed with SIGABRT in g_assertion_message()
Or not :( Looked promising for a minute. Did remove the header issue though I think. On 10 February 2014 23:47, John Lozinska wrote: > looks like a hit! > > LANG=C;sudo apt-get --purge autoremove > > https://help.ubuntu.com/community/PackageManagerTroubleshootingProcedure > > > > On 10 February 2014 23:33, John Lozinska wrote: > >> ran: ubuntu-support-status >> >> Traceback (most recent call last): >> File "/usr/bin/ubuntu-support-status", line 120, in >> with apt.Cache() as cache: >> File "/usr/lib/python3/dist-packages/apt/cache.py", line 103, in >> __init__ >> self.open(progress) >> File "/usr/lib/python3/dist-packages/apt/cache.py", line 152, in open >> self._list.read_main_list() >> >> >> >> On 10 February 2014 23:27, John Lozinska wrote: >> >>> Hope this helps >>> >>> E: The list of sources could not be read. >>> >>> Go to the repository dialog to correct the problem. >>> >>> E: _cache->open() failed, please report. >>> >>> >>> On 10 February 2014 22:48, John Lozinska wrote: >>> bash: /etc/apt/sources.list: Permission denied On 10 February 2014 22:36, John Lozinska wrote: > Also...can't load my disk drive. > > > > > On 10 February 2014 22:33, John Lozinska wrote: > >> I don't code and obviously as you can see terrible at uploading and >> writing files. It's essential I am noticing from my new experiences with >> Ubuntu. Possible to write that in 'Ubuntu for dumbies' with step by step >> directions? Sorry, but what you just said made little sense to me as to >> where to even start. I also notice these questions instantly optimise to >> Google search...which can be good and bad, depending on what files you >> are >> sharing. Also unsure of, as in the sense of hacking. @noobie >> >> >> On 10 February 2014 18:04, Seth Arnold <1275...@bugs.launchpad.net>wrote: >> >>> You have corrupted your /etc/apt/sources.list.d/upubuntu-com- >>> tor64-saucy.list file. Until you fix this file, none of the software >>> update utilities will function. Edit this file as root and fix the >>> problem. >>> >>> Thanks >>> >>> -- >>> You received this bug notification because you are subscribed to the >>> bug >>> report. >>> https://bugs.launchpad.net/bugs/1275908 >>> >>> Title: >>> pkexec crashed with SIGABRT in g_assertion_message() >>> >>> Status in "policykit-1" package in Ubuntu: >>> Invalid >>> >>> Bug description: >>> No more info to offer. >>> >>> ProblemType: Crash >>> DistroRelease: Ubuntu 14.04 >>> Package: policykit-1 0.105-4ubuntu1 >>> ProcVersionSignature: Ubuntu 3.13.0-6.23-generic 3.13.0 >>> Uname: Linux 3.13.0-6-generic i686 >>> ApportVersion: 2.13.2-0ubuntu2 >>> Architecture: i386 >>> CrashCounter: 1 >>> CurrentDesktop: Unity >>> Date: Mon Feb 3 14:17:47 2014 >>> ExecutablePath: /usr/bin/pkexec >>> InstallationDate: Installed on 2014-01-11 (23 days ago) >>> InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release i386 >>> (20130424) >>> ProcAttrCurrent: /usr/lib/lightdm/lightdm-guest-session (enforce) >>> ProcCmdline: pkexec >>> /usr/lib/gnome-settings-daemon/gsd-backlight-helper --set-brightness 3 >>> ProcEnviron: >>>PATH=(custom, no user) >>>LANGUAGE=en_CA:en >>>XDG_RUNTIME_DIR= >>>LANG=en_CA.UTF-8 >>>SHELL=/bin/bash >>> Signal: 6 >>> SourcePackage: policykit-1 >>> StacktraceTop: >>>g_assertion_message () from /lib/i386-linux-gnu/libglib-2.0.so.0 >>>g_assertion_message_expr () from >>> /lib/i386-linux-gnu/libglib-2.0.so.0 >>>?? () >>>__libc_start_main (main=0x80497f0, argc=4, argv=0xbf9de964, >>> init=0x804b0a0, fini=0x804b110, rtld_fini=0xb776c0f0 <_dl_fini>, >>> stack_end=0xbf9de95c) at libc-start.c:287 >>>?? () >>> Title: pkexec crashed with SIGABRT in g_assertion_message() >>> UpgradeStatus: Upgraded to trusty on 2014-01-18 (16 days ago) >>> UserGroups: >>> >>> To manage notifications about this bug go to: >>> >>> https://bugs.launchpad.net/ubuntu/+source/policykit-1/+bug/1275908/+subscriptions >>> >> >> > >>> >> > -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to policykit-1 in Ubuntu. https://bugs.launchpad.net/bugs/1275908 Title: pkexec crashed with SIGABRT in g_assertion_message() Status in “policykit-1” package in Ubuntu: Invalid Bug description: No more info to offer. ProblemType: Crash DistroRelease: Ubuntu 14.04 Package: policykit-1 0.105-4ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-6.23-generic 3.13.0 Uname: Linux 3.13.0-6-generic i686 ApportVersion: 2.13.2-0ubuntu2 Architecture: i386 CrashCounter: 1 CurrentDesktop: Unity
Re: [Desktop-packages] [Bug 1275908] Re: pkexec crashed with SIGABRT in g_assertion_message()
looks like a hit! LANG=C;sudo apt-get --purge autoremove https://help.ubuntu.com/community/PackageManagerTroubleshootingProcedure On 10 February 2014 23:33, John Lozinska wrote: > ran: ubuntu-support-status > > Traceback (most recent call last): > File "/usr/bin/ubuntu-support-status", line 120, in > with apt.Cache() as cache: > File "/usr/lib/python3/dist-packages/apt/cache.py", line 103, in __init__ > self.open(progress) > File "/usr/lib/python3/dist-packages/apt/cache.py", line 152, in open > self._list.read_main_list() > > > > On 10 February 2014 23:27, John Lozinska wrote: > >> Hope this helps >> >> E: The list of sources could not be read. >> >> Go to the repository dialog to correct the problem. >> >> E: _cache->open() failed, please report. >> >> >> On 10 February 2014 22:48, John Lozinska wrote: >> >>> bash: /etc/apt/sources.list: Permission denied >>> >>> >>> On 10 February 2014 22:36, John Lozinska wrote: >>> Also...can't load my disk drive. On 10 February 2014 22:33, John Lozinska wrote: > I don't code and obviously as you can see terrible at uploading and > writing files. It's essential I am noticing from my new experiences with > Ubuntu. Possible to write that in 'Ubuntu for dumbies' with step by step > directions? Sorry, but what you just said made little sense to me as to > where to even start. I also notice these questions instantly optimise to > Google search...which can be good and bad, depending on what files you are > sharing. Also unsure of, as in the sense of hacking. @noobie > > > On 10 February 2014 18:04, Seth Arnold <1275...@bugs.launchpad.net>wrote: > >> You have corrupted your /etc/apt/sources.list.d/upubuntu-com- >> tor64-saucy.list file. Until you fix this file, none of the software >> update utilities will function. Edit this file as root and fix the >> problem. >> >> Thanks >> >> -- >> You received this bug notification because you are subscribed to the >> bug >> report. >> https://bugs.launchpad.net/bugs/1275908 >> >> Title: >> pkexec crashed with SIGABRT in g_assertion_message() >> >> Status in "policykit-1" package in Ubuntu: >> Invalid >> >> Bug description: >> No more info to offer. >> >> ProblemType: Crash >> DistroRelease: Ubuntu 14.04 >> Package: policykit-1 0.105-4ubuntu1 >> ProcVersionSignature: Ubuntu 3.13.0-6.23-generic 3.13.0 >> Uname: Linux 3.13.0-6-generic i686 >> ApportVersion: 2.13.2-0ubuntu2 >> Architecture: i386 >> CrashCounter: 1 >> CurrentDesktop: Unity >> Date: Mon Feb 3 14:17:47 2014 >> ExecutablePath: /usr/bin/pkexec >> InstallationDate: Installed on 2014-01-11 (23 days ago) >> InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release i386 >> (20130424) >> ProcAttrCurrent: /usr/lib/lightdm/lightdm-guest-session (enforce) >> ProcCmdline: pkexec >> /usr/lib/gnome-settings-daemon/gsd-backlight-helper --set-brightness 3 >> ProcEnviron: >>PATH=(custom, no user) >>LANGUAGE=en_CA:en >>XDG_RUNTIME_DIR= >>LANG=en_CA.UTF-8 >>SHELL=/bin/bash >> Signal: 6 >> SourcePackage: policykit-1 >> StacktraceTop: >>g_assertion_message () from /lib/i386-linux-gnu/libglib-2.0.so.0 >>g_assertion_message_expr () from >> /lib/i386-linux-gnu/libglib-2.0.so.0 >>?? () >>__libc_start_main (main=0x80497f0, argc=4, argv=0xbf9de964, >> init=0x804b0a0, fini=0x804b110, rtld_fini=0xb776c0f0 <_dl_fini>, >> stack_end=0xbf9de95c) at libc-start.c:287 >>?? () >> Title: pkexec crashed with SIGABRT in g_assertion_message() >> UpgradeStatus: Upgraded to trusty on 2014-01-18 (16 days ago) >> UserGroups: >> >> To manage notifications about this bug go to: >> >> https://bugs.launchpad.net/ubuntu/+source/policykit-1/+bug/1275908/+subscriptions >> > > >>> >> > -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to policykit-1 in Ubuntu. https://bugs.launchpad.net/bugs/1275908 Title: pkexec crashed with SIGABRT in g_assertion_message() Status in “policykit-1” package in Ubuntu: Invalid Bug description: No more info to offer. ProblemType: Crash DistroRelease: Ubuntu 14.04 Package: policykit-1 0.105-4ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-6.23-generic 3.13.0 Uname: Linux 3.13.0-6-generic i686 ApportVersion: 2.13.2-0ubuntu2 Architecture: i386 CrashCounter: 1 CurrentDesktop: Unity Date: Mon Feb 3 14:17:47 2014 ExecutablePath: /usr/bin/pkexec InstallationDate: Installed on 2014-01-11 (23 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release i386 (20130424) ProcAttrCurrent: /usr/lib/lightdm/lightdm-guest-session (enforce) ProcCmdli
Re: [Desktop-packages] [Bug 1275908] Re: pkexec crashed with SIGABRT in g_assertion_message()
ran: ubuntu-support-status Traceback (most recent call last): File "/usr/bin/ubuntu-support-status", line 120, in with apt.Cache() as cache: File "/usr/lib/python3/dist-packages/apt/cache.py", line 103, in __init__ self.open(progress) File "/usr/lib/python3/dist-packages/apt/cache.py", line 152, in open self._list.read_main_list() On 10 February 2014 23:27, John Lozinska wrote: > Hope this helps > > E: The list of sources could not be read. > > Go to the repository dialog to correct the problem. > > E: _cache->open() failed, please report. > > > On 10 February 2014 22:48, John Lozinska wrote: > >> bash: /etc/apt/sources.list: Permission denied >> >> >> On 10 February 2014 22:36, John Lozinska wrote: >> >>> Also...can't load my disk drive. >>> >>> >>> >>> >>> On 10 February 2014 22:33, John Lozinska wrote: >>> I don't code and obviously as you can see terrible at uploading and writing files. It's essential I am noticing from my new experiences with Ubuntu. Possible to write that in 'Ubuntu for dumbies' with step by step directions? Sorry, but what you just said made little sense to me as to where to even start. I also notice these questions instantly optimise to Google search...which can be good and bad, depending on what files you are sharing. Also unsure of, as in the sense of hacking. @noobie On 10 February 2014 18:04, Seth Arnold <1275...@bugs.launchpad.net>wrote: > You have corrupted your /etc/apt/sources.list.d/upubuntu-com- > tor64-saucy.list file. Until you fix this file, none of the software > update utilities will function. Edit this file as root and fix the > problem. > > Thanks > > -- > You received this bug notification because you are subscribed to the > bug > report. > https://bugs.launchpad.net/bugs/1275908 > > Title: > pkexec crashed with SIGABRT in g_assertion_message() > > Status in "policykit-1" package in Ubuntu: > Invalid > > Bug description: > No more info to offer. > > ProblemType: Crash > DistroRelease: Ubuntu 14.04 > Package: policykit-1 0.105-4ubuntu1 > ProcVersionSignature: Ubuntu 3.13.0-6.23-generic 3.13.0 > Uname: Linux 3.13.0-6-generic i686 > ApportVersion: 2.13.2-0ubuntu2 > Architecture: i386 > CrashCounter: 1 > CurrentDesktop: Unity > Date: Mon Feb 3 14:17:47 2014 > ExecutablePath: /usr/bin/pkexec > InstallationDate: Installed on 2014-01-11 (23 days ago) > InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release i386 > (20130424) > ProcAttrCurrent: /usr/lib/lightdm/lightdm-guest-session (enforce) > ProcCmdline: pkexec > /usr/lib/gnome-settings-daemon/gsd-backlight-helper --set-brightness 3 > ProcEnviron: >PATH=(custom, no user) >LANGUAGE=en_CA:en >XDG_RUNTIME_DIR= >LANG=en_CA.UTF-8 >SHELL=/bin/bash > Signal: 6 > SourcePackage: policykit-1 > StacktraceTop: >g_assertion_message () from /lib/i386-linux-gnu/libglib-2.0.so.0 >g_assertion_message_expr () from > /lib/i386-linux-gnu/libglib-2.0.so.0 >?? () >__libc_start_main (main=0x80497f0, argc=4, argv=0xbf9de964, > init=0x804b0a0, fini=0x804b110, rtld_fini=0xb776c0f0 <_dl_fini>, > stack_end=0xbf9de95c) at libc-start.c:287 >?? () > Title: pkexec crashed with SIGABRT in g_assertion_message() > UpgradeStatus: Upgraded to trusty on 2014-01-18 (16 days ago) > UserGroups: > > To manage notifications about this bug go to: > > https://bugs.launchpad.net/ubuntu/+source/policykit-1/+bug/1275908/+subscriptions > >>> >> > -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to policykit-1 in Ubuntu. https://bugs.launchpad.net/bugs/1275908 Title: pkexec crashed with SIGABRT in g_assertion_message() Status in “policykit-1” package in Ubuntu: Invalid Bug description: No more info to offer. ProblemType: Crash DistroRelease: Ubuntu 14.04 Package: policykit-1 0.105-4ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-6.23-generic 3.13.0 Uname: Linux 3.13.0-6-generic i686 ApportVersion: 2.13.2-0ubuntu2 Architecture: i386 CrashCounter: 1 CurrentDesktop: Unity Date: Mon Feb 3 14:17:47 2014 ExecutablePath: /usr/bin/pkexec InstallationDate: Installed on 2014-01-11 (23 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release i386 (20130424) ProcAttrCurrent: /usr/lib/lightdm/lightdm-guest-session (enforce) ProcCmdline: pkexec /usr/lib/gnome-settings-daemon/gsd-backlight-helper --set-brightness 3 ProcEnviron: PATH=(custom, no user) LANGUAGE=en_CA:en XDG_RUNTIME_DIR= LANG=en_CA.UTF-8 SHELL=/bin/bash Signal: 6 SourcePackage: policykit-1 StacktraceTop: g_assertion_message () from /lib/i386-linux-gnu/
Re: [Desktop-packages] [Bug 1275908] Re: pkexec crashed with SIGABRT in g_assertion_message()
Hope this helps E: The list of sources could not be read. Go to the repository dialog to correct the problem. E: _cache->open() failed, please report. On 10 February 2014 22:48, John Lozinska wrote: > bash: /etc/apt/sources.list: Permission denied > > > On 10 February 2014 22:36, John Lozinska wrote: > >> Also...can't load my disk drive. >> >> >> >> >> On 10 February 2014 22:33, John Lozinska wrote: >> >>> I don't code and obviously as you can see terrible at uploading and >>> writing files. It's essential I am noticing from my new experiences with >>> Ubuntu. Possible to write that in 'Ubuntu for dumbies' with step by step >>> directions? Sorry, but what you just said made little sense to me as to >>> where to even start. I also notice these questions instantly optimise to >>> Google search...which can be good and bad, depending on what files you are >>> sharing. Also unsure of, as in the sense of hacking. @noobie >>> >>> >>> On 10 February 2014 18:04, Seth Arnold <1275...@bugs.launchpad.net>wrote: >>> You have corrupted your /etc/apt/sources.list.d/upubuntu-com- tor64-saucy.list file. Until you fix this file, none of the software update utilities will function. Edit this file as root and fix the problem. Thanks -- You received this bug notification because you are subscribed to the bug report. https://bugs.launchpad.net/bugs/1275908 Title: pkexec crashed with SIGABRT in g_assertion_message() Status in "policykit-1" package in Ubuntu: Invalid Bug description: No more info to offer. ProblemType: Crash DistroRelease: Ubuntu 14.04 Package: policykit-1 0.105-4ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-6.23-generic 3.13.0 Uname: Linux 3.13.0-6-generic i686 ApportVersion: 2.13.2-0ubuntu2 Architecture: i386 CrashCounter: 1 CurrentDesktop: Unity Date: Mon Feb 3 14:17:47 2014 ExecutablePath: /usr/bin/pkexec InstallationDate: Installed on 2014-01-11 (23 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release i386 (20130424) ProcAttrCurrent: /usr/lib/lightdm/lightdm-guest-session (enforce) ProcCmdline: pkexec /usr/lib/gnome-settings-daemon/gsd-backlight-helper --set-brightness 3 ProcEnviron: PATH=(custom, no user) LANGUAGE=en_CA:en XDG_RUNTIME_DIR= LANG=en_CA.UTF-8 SHELL=/bin/bash Signal: 6 SourcePackage: policykit-1 StacktraceTop: g_assertion_message () from /lib/i386-linux-gnu/libglib-2.0.so.0 g_assertion_message_expr () from /lib/i386-linux-gnu/libglib-2.0.so.0 ?? () __libc_start_main (main=0x80497f0, argc=4, argv=0xbf9de964, init=0x804b0a0, fini=0x804b110, rtld_fini=0xb776c0f0 <_dl_fini>, stack_end=0xbf9de95c) at libc-start.c:287 ?? () Title: pkexec crashed with SIGABRT in g_assertion_message() UpgradeStatus: Upgraded to trusty on 2014-01-18 (16 days ago) UserGroups: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/policykit-1/+bug/1275908/+subscriptions >>> >>> >> > -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to policykit-1 in Ubuntu. https://bugs.launchpad.net/bugs/1275908 Title: pkexec crashed with SIGABRT in g_assertion_message() Status in “policykit-1” package in Ubuntu: Invalid Bug description: No more info to offer. ProblemType: Crash DistroRelease: Ubuntu 14.04 Package: policykit-1 0.105-4ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-6.23-generic 3.13.0 Uname: Linux 3.13.0-6-generic i686 ApportVersion: 2.13.2-0ubuntu2 Architecture: i386 CrashCounter: 1 CurrentDesktop: Unity Date: Mon Feb 3 14:17:47 2014 ExecutablePath: /usr/bin/pkexec InstallationDate: Installed on 2014-01-11 (23 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release i386 (20130424) ProcAttrCurrent: /usr/lib/lightdm/lightdm-guest-session (enforce) ProcCmdline: pkexec /usr/lib/gnome-settings-daemon/gsd-backlight-helper --set-brightness 3 ProcEnviron: PATH=(custom, no user) LANGUAGE=en_CA:en XDG_RUNTIME_DIR= LANG=en_CA.UTF-8 SHELL=/bin/bash Signal: 6 SourcePackage: policykit-1 StacktraceTop: g_assertion_message () from /lib/i386-linux-gnu/libglib-2.0.so.0 g_assertion_message_expr () from /lib/i386-linux-gnu/libglib-2.0.so.0 ?? () __libc_start_main (main=0x80497f0, argc=4, argv=0xbf9de964, init=0x804b0a0, fini=0x804b110, rtld_fini=0xb776c0f0 <_dl_fini>, stack_end=0xbf9de95c) at libc-start.c:287 ?? () Title: pkexec crashed with SIGABRT in g_assertion_message() UpgradeStatus: Upgraded to trusty on 2014-01-18 (16 days ago) UserGroups: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/policykit-1/+bu
Re: [Desktop-packages] [Bug 1275908] Re: pkexec crashed with SIGABRT in g_assertion_message()
bash: /etc/apt/sources.list: Permission denied On 10 February 2014 22:36, John Lozinska wrote: > Also...can't load my disk drive. > > > > > On 10 February 2014 22:33, John Lozinska wrote: > >> I don't code and obviously as you can see terrible at uploading and >> writing files. It's essential I am noticing from my new experiences with >> Ubuntu. Possible to write that in 'Ubuntu for dumbies' with step by step >> directions? Sorry, but what you just said made little sense to me as to >> where to even start. I also notice these questions instantly optimise to >> Google search...which can be good and bad, depending on what files you are >> sharing. Also unsure of, as in the sense of hacking. @noobie >> >> >> On 10 February 2014 18:04, Seth Arnold <1275...@bugs.launchpad.net>wrote: >> >>> You have corrupted your /etc/apt/sources.list.d/upubuntu-com- >>> tor64-saucy.list file. Until you fix this file, none of the software >>> update utilities will function. Edit this file as root and fix the >>> problem. >>> >>> Thanks >>> >>> -- >>> You received this bug notification because you are subscribed to the bug >>> report. >>> https://bugs.launchpad.net/bugs/1275908 >>> >>> Title: >>> pkexec crashed with SIGABRT in g_assertion_message() >>> >>> Status in "policykit-1" package in Ubuntu: >>> Invalid >>> >>> Bug description: >>> No more info to offer. >>> >>> ProblemType: Crash >>> DistroRelease: Ubuntu 14.04 >>> Package: policykit-1 0.105-4ubuntu1 >>> ProcVersionSignature: Ubuntu 3.13.0-6.23-generic 3.13.0 >>> Uname: Linux 3.13.0-6-generic i686 >>> ApportVersion: 2.13.2-0ubuntu2 >>> Architecture: i386 >>> CrashCounter: 1 >>> CurrentDesktop: Unity >>> Date: Mon Feb 3 14:17:47 2014 >>> ExecutablePath: /usr/bin/pkexec >>> InstallationDate: Installed on 2014-01-11 (23 days ago) >>> InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release i386 >>> (20130424) >>> ProcAttrCurrent: /usr/lib/lightdm/lightdm-guest-session (enforce) >>> ProcCmdline: pkexec >>> /usr/lib/gnome-settings-daemon/gsd-backlight-helper --set-brightness 3 >>> ProcEnviron: >>>PATH=(custom, no user) >>>LANGUAGE=en_CA:en >>>XDG_RUNTIME_DIR= >>>LANG=en_CA.UTF-8 >>>SHELL=/bin/bash >>> Signal: 6 >>> SourcePackage: policykit-1 >>> StacktraceTop: >>>g_assertion_message () from /lib/i386-linux-gnu/libglib-2.0.so.0 >>>g_assertion_message_expr () from /lib/i386-linux-gnu/libglib-2.0.so.0 >>>?? () >>>__libc_start_main (main=0x80497f0, argc=4, argv=0xbf9de964, >>> init=0x804b0a0, fini=0x804b110, rtld_fini=0xb776c0f0 <_dl_fini>, >>> stack_end=0xbf9de95c) at libc-start.c:287 >>>?? () >>> Title: pkexec crashed with SIGABRT in g_assertion_message() >>> UpgradeStatus: Upgraded to trusty on 2014-01-18 (16 days ago) >>> UserGroups: >>> >>> To manage notifications about this bug go to: >>> >>> https://bugs.launchpad.net/ubuntu/+source/policykit-1/+bug/1275908/+subscriptions >>> >> >> > -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to policykit-1 in Ubuntu. https://bugs.launchpad.net/bugs/1275908 Title: pkexec crashed with SIGABRT in g_assertion_message() Status in “policykit-1” package in Ubuntu: Invalid Bug description: No more info to offer. ProblemType: Crash DistroRelease: Ubuntu 14.04 Package: policykit-1 0.105-4ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-6.23-generic 3.13.0 Uname: Linux 3.13.0-6-generic i686 ApportVersion: 2.13.2-0ubuntu2 Architecture: i386 CrashCounter: 1 CurrentDesktop: Unity Date: Mon Feb 3 14:17:47 2014 ExecutablePath: /usr/bin/pkexec InstallationDate: Installed on 2014-01-11 (23 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release i386 (20130424) ProcAttrCurrent: /usr/lib/lightdm/lightdm-guest-session (enforce) ProcCmdline: pkexec /usr/lib/gnome-settings-daemon/gsd-backlight-helper --set-brightness 3 ProcEnviron: PATH=(custom, no user) LANGUAGE=en_CA:en XDG_RUNTIME_DIR= LANG=en_CA.UTF-8 SHELL=/bin/bash Signal: 6 SourcePackage: policykit-1 StacktraceTop: g_assertion_message () from /lib/i386-linux-gnu/libglib-2.0.so.0 g_assertion_message_expr () from /lib/i386-linux-gnu/libglib-2.0.so.0 ?? () __libc_start_main (main=0x80497f0, argc=4, argv=0xbf9de964, init=0x804b0a0, fini=0x804b110, rtld_fini=0xb776c0f0 <_dl_fini>, stack_end=0xbf9de95c) at libc-start.c:287 ?? () Title: pkexec crashed with SIGABRT in g_assertion_message() UpgradeStatus: Upgraded to trusty on 2014-01-18 (16 days ago) UserGroups: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/policykit-1/+bug/1275908/+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 1275908] Re: pkexec crashed with SIGABRT in g_assertion_message()
I don't code and obviously as you can see terrible at uploading and writing files. It's essential I am noticing from my new experiences with Ubuntu. Possible to write that in 'Ubuntu for dumbies' with step by step directions? Sorry, but what you just said made little sense to me as to where to even start. I also notice these questions instantly optimise to Google search...which can be good and bad, depending on what files you are sharing. Also unsure of, as in the sense of hacking. @noobie On 10 February 2014 18:04, Seth Arnold <1275...@bugs.launchpad.net> wrote: > You have corrupted your /etc/apt/sources.list.d/upubuntu-com- > tor64-saucy.list file. Until you fix this file, none of the software > update utilities will function. Edit this file as root and fix the > problem. > > Thanks > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1275908 > > Title: > pkexec crashed with SIGABRT in g_assertion_message() > > Status in "policykit-1" package in Ubuntu: > Invalid > > Bug description: > No more info to offer. > > ProblemType: Crash > DistroRelease: Ubuntu 14.04 > Package: policykit-1 0.105-4ubuntu1 > ProcVersionSignature: Ubuntu 3.13.0-6.23-generic 3.13.0 > Uname: Linux 3.13.0-6-generic i686 > ApportVersion: 2.13.2-0ubuntu2 > Architecture: i386 > CrashCounter: 1 > CurrentDesktop: Unity > Date: Mon Feb 3 14:17:47 2014 > ExecutablePath: /usr/bin/pkexec > InstallationDate: Installed on 2014-01-11 (23 days ago) > InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release i386 > (20130424) > ProcAttrCurrent: /usr/lib/lightdm/lightdm-guest-session (enforce) > ProcCmdline: pkexec /usr/lib/gnome-settings-daemon/gsd-backlight-helper > --set-brightness 3 > ProcEnviron: >PATH=(custom, no user) >LANGUAGE=en_CA:en >XDG_RUNTIME_DIR= >LANG=en_CA.UTF-8 >SHELL=/bin/bash > Signal: 6 > SourcePackage: policykit-1 > StacktraceTop: >g_assertion_message () from /lib/i386-linux-gnu/libglib-2.0.so.0 >g_assertion_message_expr () from /lib/i386-linux-gnu/libglib-2.0.so.0 >?? () >__libc_start_main (main=0x80497f0, argc=4, argv=0xbf9de964, > init=0x804b0a0, fini=0x804b110, rtld_fini=0xb776c0f0 <_dl_fini>, > stack_end=0xbf9de95c) at libc-start.c:287 >?? () > Title: pkexec crashed with SIGABRT in g_assertion_message() > UpgradeStatus: Upgraded to trusty on 2014-01-18 (16 days ago) > UserGroups: > > To manage notifications about this bug go to: > > https://bugs.launchpad.net/ubuntu/+source/policykit-1/+bug/1275908/+subscriptions > -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to policykit-1 in Ubuntu. https://bugs.launchpad.net/bugs/1275908 Title: pkexec crashed with SIGABRT in g_assertion_message() Status in “policykit-1” package in Ubuntu: Invalid Bug description: No more info to offer. ProblemType: Crash DistroRelease: Ubuntu 14.04 Package: policykit-1 0.105-4ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-6.23-generic 3.13.0 Uname: Linux 3.13.0-6-generic i686 ApportVersion: 2.13.2-0ubuntu2 Architecture: i386 CrashCounter: 1 CurrentDesktop: Unity Date: Mon Feb 3 14:17:47 2014 ExecutablePath: /usr/bin/pkexec InstallationDate: Installed on 2014-01-11 (23 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release i386 (20130424) ProcAttrCurrent: /usr/lib/lightdm/lightdm-guest-session (enforce) ProcCmdline: pkexec /usr/lib/gnome-settings-daemon/gsd-backlight-helper --set-brightness 3 ProcEnviron: PATH=(custom, no user) LANGUAGE=en_CA:en XDG_RUNTIME_DIR= LANG=en_CA.UTF-8 SHELL=/bin/bash Signal: 6 SourcePackage: policykit-1 StacktraceTop: g_assertion_message () from /lib/i386-linux-gnu/libglib-2.0.so.0 g_assertion_message_expr () from /lib/i386-linux-gnu/libglib-2.0.so.0 ?? () __libc_start_main (main=0x80497f0, argc=4, argv=0xbf9de964, init=0x804b0a0, fini=0x804b110, rtld_fini=0xb776c0f0 <_dl_fini>, stack_end=0xbf9de95c) at libc-start.c:287 ?? () Title: pkexec crashed with SIGABRT in g_assertion_message() UpgradeStatus: Upgraded to trusty on 2014-01-18 (16 days ago) UserGroups: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/policykit-1/+bug/1275908/+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 1275908] Re: pkexec crashed with SIGABRT in g_assertion_message()
Also...can't load my disk drive. On 10 February 2014 22:33, John Lozinska wrote: > I don't code and obviously as you can see terrible at uploading and > writing files. It's essential I am noticing from my new experiences with > Ubuntu. Possible to write that in 'Ubuntu for dumbies' with step by step > directions? Sorry, but what you just said made little sense to me as to > where to even start. I also notice these questions instantly optimise to > Google search...which can be good and bad, depending on what files you are > sharing. Also unsure of, as in the sense of hacking. @noobie > > > On 10 February 2014 18:04, Seth Arnold <1275...@bugs.launchpad.net> wrote: > >> You have corrupted your /etc/apt/sources.list.d/upubuntu-com- >> tor64-saucy.list file. Until you fix this file, none of the software >> update utilities will function. Edit this file as root and fix the >> problem. >> >> Thanks >> >> -- >> You received this bug notification because you are subscribed to the bug >> report. >> https://bugs.launchpad.net/bugs/1275908 >> >> Title: >> pkexec crashed with SIGABRT in g_assertion_message() >> >> Status in "policykit-1" package in Ubuntu: >> Invalid >> >> Bug description: >> No more info to offer. >> >> ProblemType: Crash >> DistroRelease: Ubuntu 14.04 >> Package: policykit-1 0.105-4ubuntu1 >> ProcVersionSignature: Ubuntu 3.13.0-6.23-generic 3.13.0 >> Uname: Linux 3.13.0-6-generic i686 >> ApportVersion: 2.13.2-0ubuntu2 >> Architecture: i386 >> CrashCounter: 1 >> CurrentDesktop: Unity >> Date: Mon Feb 3 14:17:47 2014 >> ExecutablePath: /usr/bin/pkexec >> InstallationDate: Installed on 2014-01-11 (23 days ago) >> InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release i386 >> (20130424) >> ProcAttrCurrent: /usr/lib/lightdm/lightdm-guest-session (enforce) >> ProcCmdline: pkexec /usr/lib/gnome-settings-daemon/gsd-backlight-helper >> --set-brightness 3 >> ProcEnviron: >>PATH=(custom, no user) >>LANGUAGE=en_CA:en >>XDG_RUNTIME_DIR= >>LANG=en_CA.UTF-8 >>SHELL=/bin/bash >> Signal: 6 >> SourcePackage: policykit-1 >> StacktraceTop: >>g_assertion_message () from /lib/i386-linux-gnu/libglib-2.0.so.0 >>g_assertion_message_expr () from /lib/i386-linux-gnu/libglib-2.0.so.0 >>?? () >>__libc_start_main (main=0x80497f0, argc=4, argv=0xbf9de964, >> init=0x804b0a0, fini=0x804b110, rtld_fini=0xb776c0f0 <_dl_fini>, >> stack_end=0xbf9de95c) at libc-start.c:287 >>?? () >> Title: pkexec crashed with SIGABRT in g_assertion_message() >> UpgradeStatus: Upgraded to trusty on 2014-01-18 (16 days ago) >> UserGroups: >> >> To manage notifications about this bug go to: >> >> https://bugs.launchpad.net/ubuntu/+source/policykit-1/+bug/1275908/+subscriptions >> > > ** Attachment added: "Error List - Operating System Find Application Online For Software.odt" https://bugs.launchpad.net/bugs/1275908/+attachment/3976445/+files/Error%20List%20-%20Operating%20System%20Find%20Application%20Online%20For%20Software.odt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to policykit-1 in Ubuntu. https://bugs.launchpad.net/bugs/1275908 Title: pkexec crashed with SIGABRT in g_assertion_message() Status in “policykit-1” package in Ubuntu: Invalid Bug description: No more info to offer. ProblemType: Crash DistroRelease: Ubuntu 14.04 Package: policykit-1 0.105-4ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-6.23-generic 3.13.0 Uname: Linux 3.13.0-6-generic i686 ApportVersion: 2.13.2-0ubuntu2 Architecture: i386 CrashCounter: 1 CurrentDesktop: Unity Date: Mon Feb 3 14:17:47 2014 ExecutablePath: /usr/bin/pkexec InstallationDate: Installed on 2014-01-11 (23 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release i386 (20130424) ProcAttrCurrent: /usr/lib/lightdm/lightdm-guest-session (enforce) ProcCmdline: pkexec /usr/lib/gnome-settings-daemon/gsd-backlight-helper --set-brightness 3 ProcEnviron: PATH=(custom, no user) LANGUAGE=en_CA:en XDG_RUNTIME_DIR= LANG=en_CA.UTF-8 SHELL=/bin/bash Signal: 6 SourcePackage: policykit-1 StacktraceTop: g_assertion_message () from /lib/i386-linux-gnu/libglib-2.0.so.0 g_assertion_message_expr () from /lib/i386-linux-gnu/libglib-2.0.so.0 ?? () __libc_start_main (main=0x80497f0, argc=4, argv=0xbf9de964, init=0x804b0a0, fini=0x804b110, rtld_fini=0xb776c0f0 <_dl_fini>, stack_end=0xbf9de95c) at libc-start.c:287 ?? () Title: pkexec crashed with SIGABRT in g_assertion_message() UpgradeStatus: Upgraded to trusty on 2014-01-18 (16 days ago) UserGroups: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/policykit-1/+bug/1275908/+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.
Re: [Desktop-packages] [Bug 1275908] Re: pkexec crashed with SIGABRT in g_assertion_message()
Software Update Manager wasn't working, found a post that said to: run: software-center 2014-02-10 17:28:21,282 - softwarecenter.ui.gtk3.app - INFO - setting up proxy 'None' /usr/share/software-center/softwarecenter/ui/gtk3/widgets/spinner.py:52: PyGTKDeprecationWarning: Using positional arguments with the GObject constructor has been deprecated. Please specify keywords for n_rows, n_columns, homogeneous or use a class specific constructor. See: https://wiki.gnome.org/PyGObject/InitializerDeprecations spinner_table = Gtk.Table(3, 3, False) /usr/share/software-center/softwarecenter/ui/gtk3/widgets/spinner.py:101: PyGTKDeprecationWarning: Using positional arguments with the GObject constructor has been deprecated. Please specify keywords for label or use a class specific constructor. See: https://wiki.gnome.org/PyGObject/InitializerDeprecations self.append_page(content, Gtk.Label("content")) /usr/share/software-center/softwarecenter/ui/gtk3/widgets/spinner.py:102: PyGTKDeprecationWarning: Using positional arguments with the GObject constructor has been deprecated. Please specify keywords for label or use a class specific constructor. See: https://wiki.gnome.org/PyGObject/InitializerDeprecations self.append_page(self.spinner_view, Gtk.Label("spinner")) /usr/share/software-center/softwarecenter/ui/gtk3/panes/historypane.py:90: PyGTKDeprecationWarning: Using positional arguments with the GObject constructor has been deprecated. Please specify keywords for name, label, tooltip, stock_id, value or use a class specific constructor. See: https://wiki.gnome.org/PyGObject/InitializerDeprecations None, self.ALL) /usr/share/software-center/softwarecenter/ui/gtk3/panes/historypane.py:96: PyGTKDeprecationWarning: Using positional arguments with the GObject constructor has been deprecated. Please specify keywords for name, label, tooltip, stock_id, value or use a class specific constructor. See: https://wiki.gnome.org/PyGObject/InitializerDeprecations _('Installations'), None, None, self.INSTALLED) /usr/share/software-center/softwarecenter/ui/gtk3/panes/historypane.py:102: PyGTKDeprecationWarning: Using positional arguments with the GObject constructor has been deprecated. Please specify keywords for name, label, tooltip, stock_id, value or use a class specific constructor. See: https://wiki.gnome.org/PyGObject/InitializerDeprecations 'filter_upgrads', _('Updates'), None, None, self.UPGRADED) /usr/share/software-center/softwarecenter/ui/gtk3/panes/historypane.py:108: PyGTKDeprecationWarning: Using positional arguments with the GObject constructor has been deprecated. Please specify keywords for name, label, tooltip, stock_id, value or use a class specific constructor. See: https://wiki.gnome.org/PyGObject/InitializerDeprecations 'filter_removals', _('Removals'), None, None, self.REMOVED) 2014-02-10 17:28:22,745 - softwarecenter.backend.reviews - WARNING - Could not get usefulness from server, no username in config file 2014-02-10 17:28:22,752 - softwarecenter.plugin - INFO - activating plugin '' 2014-02-10 17:28:22,786 - softwarecenter.fixme - WARNING - logs to the root logger: '('/usr/lib/python2.7/dist-packages/gi/importer.py', 51, 'find_module')' 2014-02-10 17:28:22,786 - root - ERROR - Could not find any typelib for LaunchpadIntegration 2014-02-10 17:28:22,923 - softwarecenter.db.pkginfo_impl.aptcache - INFO - aptcache.open() Traceback (most recent call last): File "/usr/share/software-center/softwarecenter/db/pkginfo_impl/aptcache.py", line 261, in open self._cache = apt.Cache(progress) File "/usr/lib/python2.7/dist-packages/apt/cache.py", line 103, in __init__ self.open(progress) File "/usr/lib/python2.7/dist-packages/apt/cache.py", line 148, in open self._cache = apt_pkg.Cache(progress) SystemError: E:Type 'gksudo' is not known on line 1 in source list /etc/apt/sources.list.d/upubuntu-com-tor64-saucy.list, E:The list of sources could not be read., E:The package lists or status file could not be parsed or opened. /usr/share/software-center/softwarecenter/ui/gtk3/views/appdetailsview.py:702: PyGTKDeprecationWarning: Using positional arguments with the GObject constructor has been deprecated. Please specify keywords for label or use a class specific constructor. See: https://wiki.gnome.org/PyGObject/InitializerDeprecations self.label_price = Gtk.Label(_("Free")) /usr/share/software-center/softwarecenter/ui/gtk3/views/appdetailsview.py:707: PyGTKDeprecationWarning: Using positional arguments with the GObject constructor has been deprecated. Please specify keywords for label or use a class specific constructor. See: https://wiki.gnome.org/PyGObject/InitializerDeprecations self.button_apply = Gtk.Button(_("Apply Changes")) /usr/share/software-center/softwarecenter/ui/gtk3/views/appdetailsview.py:709: PyGTKDeprecationWarning: Using positional arguments with the GObject constructor has been deprecated. Please specify keywords for label or use a class specific constructor. See: https://
Re: [Desktop-packages] [Bug 1275908] Re: pkexec crashed with SIGABRT in g_assertion_message()
Did a 'sudo do-release-upgrade' Checking for a new Ubuntu release Traceback (most recent call last): File "/usr/bin/do-release-upgrade", line 111, in useProposed=options.proposed_release) File "/usr/lib/python3/dist-packages/UpdateManager/Core/MetaRelease.py", line 93, in __init__ cache = apt.Cache() File "/usr/lib/python3/dist-packages/apt/cache.py", line 103, in __init__ self.open(progress) File "/usr/lib/python3/dist-packages/apt/cache.py", line 152, in open self._list.read_main_list() SystemError: E:Type 'gksudo' is not known on line 1 in source list /etc/apt/sources.list.d/upubuntu-com-tor64-saucy.list On 10 February 2014 17:12, John Lozinska wrote: > Further when trying to upgrade > > E: Could not open lock file /var/lib/dpkg/lock - open (13: Permission > denied) > E: Unable to lock the administration directory (/var/lib/dpkg/), are you > root? > > With no option of giving y/n > > > On 10 February 2014 17:05, John Lozinska wrote: > >> usr/bin/software-properties-gtk >> >> >> On 10 February 2014 17:03, John Lozinska wrote: >> >>> My System says: >>> >>> Processor: AMD E-350 Processor × 2 >>> >>> Why x2? Normal? >>> >>> >>> >>> On 10 February 2014 17:02, John Lozinska wrote: >>> Tried to update software E:Type 'gksudo' is not known on line 1 in source list /etc/apt/sources.list.d/upubuntu-com-tor64-saucy.list, E:The list of sources could not be read., E:The package lists or status file could not be parsed or opened. On 10 February 2014 16:51, John Lozinska wrote: > E: Type 'gksudo' is not known on line 1 in source list > /etc/apt/sources.list.d/upubuntu-com-tor64-saucy.list > E: The list of sources could not be read. > videotron@videotron-Lenovo-B575:~$ gksudo apt-get upgrade > Reading package lists... Error! > videotron@videotron-Lenovo-B575:~$ gksudo apt-get upgrade > Reading package lists... Done > Building dependency tree > Reading state information... Done > Calculating upgrade... Done > The following packages were automatically installed and are no longer > required: > gir1.2-ibus-1.0 libgweather-3-3 libhud-client2 libpoppler43 libwebp4 > linux-headers-3.13.0-4 linux-headers-3.13.0-4-generic > linux-image-3.11.0-15-generic linux-image-3.13.0-4-generic > linux-image-extra-3.11.0-15-generic > linux-image-extra-3.13.0-4-generic > Use 'apt-get autoremove' to remove them. > 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. > > When I did a previous action to access the sources list, it did come > up as shown below. I do not know what to do with that? > > # See http://help.ubuntu.com/community/UpgradeNotes for how to > upgrade to > # newer versions of the distribution. > deb http://ca.archive.ubuntu.com/ubuntu/ trusty main restricted > deb-src http://ca.archive.ubuntu.com/ubuntu/ trusty main restricted > > ## Major bug fix updates produced after the final release of the > ## distribution. > deb http://ca.archive.ubuntu.com/ubuntu/ trusty-updates main > restricted > deb-src http://ca.archive.ubuntu.com/ubuntu/ trusty-updates main > restricted > > ## N.B. software from this repository is ENTIRELY UNSUPPORTED by the > Ubuntu > ## team. Also, please note that software in universe WILL NOT receive > any > ## review or updates from the Ubuntu security team. > deb http://ca.archive.ubuntu.com/ubuntu/ trusty universe > deb-src http://ca.archive.ubuntu.com/ubuntu/ trusty universe > deb http://ca.archive.ubuntu.com/ubuntu/ trusty-updates universe > deb-src http://ca.archive.ubuntu.com/ubuntu/ trusty-updates universe > > ## N.B. software from this repository is ENTIRELY UNSUPPORTED by the > Ubuntu > ## team, and may not be under a free licence. Please satisfy yourself > as to > ## your rights to use the software. Also, please note that software in > ## multiverse WILL NOT receive any review or updates from the Ubuntu > ## security team. > deb http://ca.archive.ubuntu.com/ubuntu/ trusty multiverse > deb-src http://ca.archive.ubuntu.com/ubuntu/ trusty multiverse > deb http://ca.archive.ubuntu.com/ubuntu/ trusty-updates multiverse > deb-src http://ca.archive.ubuntu.com/ubuntu/ trusty-updates multiverse > > ## N.B. software from this repository may not have been tested as > ## extensively as that contained in the main release, although it > includes > ## newer versions of some applications which may provide useful > features. > ## Also, please note that software in backports WILL NOT receive any > review > ## or updates from the Ubuntu security team. > > deb http://security.ubuntu.com/ubuntu trusty-security main restricted > deb-src http://security.ubuntu.com/ubuntu trusty-security main > restricted > deb http://security.ubuntu.com/ubu
Re: [Desktop-packages] [Bug 1275908] Re: pkexec crashed with SIGABRT in g_assertion_message()
Further when trying to upgrade E: Could not open lock file /var/lib/dpkg/lock - open (13: Permission denied) E: Unable to lock the administration directory (/var/lib/dpkg/), are you root? With no option of giving y/n On 10 February 2014 17:05, John Lozinska wrote: > usr/bin/software-properties-gtk > > > On 10 February 2014 17:03, John Lozinska wrote: > >> My System says: >> >> Processor: AMD E-350 Processor × 2 >> >> Why x2? Normal? >> >> >> >> On 10 February 2014 17:02, John Lozinska wrote: >> >>> Tried to update software >>> >>> E:Type 'gksudo' is not known on line 1 in source list >>> /etc/apt/sources.list.d/upubuntu-com-tor64-saucy.list, E:The list of >>> sources could not be read., E:The package lists or status file could not be >>> parsed or opened. >>> >>> >>> On 10 February 2014 16:51, John Lozinska wrote: >>> E: Type 'gksudo' is not known on line 1 in source list /etc/apt/sources.list.d/upubuntu-com-tor64-saucy.list E: The list of sources could not be read. videotron@videotron-Lenovo-B575:~$ gksudo apt-get upgrade Reading package lists... Error! videotron@videotron-Lenovo-B575:~$ gksudo apt-get upgrade Reading package lists... Done Building dependency tree Reading state information... Done Calculating upgrade... Done The following packages were automatically installed and are no longer required: gir1.2-ibus-1.0 libgweather-3-3 libhud-client2 libpoppler43 libwebp4 linux-headers-3.13.0-4 linux-headers-3.13.0-4-generic linux-image-3.11.0-15-generic linux-image-3.13.0-4-generic linux-image-extra-3.11.0-15-generic linux-image-extra-3.13.0-4-generic Use 'apt-get autoremove' to remove them. 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. When I did a previous action to access the sources list, it did come up as shown below. I do not know what to do with that? # See http://help.ubuntu.com/community/UpgradeNotes for how to upgrade to # newer versions of the distribution. deb http://ca.archive.ubuntu.com/ubuntu/ trusty main restricted deb-src http://ca.archive.ubuntu.com/ubuntu/ trusty main restricted ## Major bug fix updates produced after the final release of the ## distribution. deb http://ca.archive.ubuntu.com/ubuntu/ trusty-updates main restricted deb-src http://ca.archive.ubuntu.com/ubuntu/ trusty-updates main restricted ## N.B. software from this repository is ENTIRELY UNSUPPORTED by the Ubuntu ## team. Also, please note that software in universe WILL NOT receive any ## review or updates from the Ubuntu security team. deb http://ca.archive.ubuntu.com/ubuntu/ trusty universe deb-src http://ca.archive.ubuntu.com/ubuntu/ trusty universe deb http://ca.archive.ubuntu.com/ubuntu/ trusty-updates universe deb-src http://ca.archive.ubuntu.com/ubuntu/ trusty-updates universe ## N.B. software from this repository is ENTIRELY UNSUPPORTED by the Ubuntu ## team, and may not be under a free licence. Please satisfy yourself as to ## your rights to use the software. Also, please note that software in ## multiverse WILL NOT receive any review or updates from the Ubuntu ## security team. deb http://ca.archive.ubuntu.com/ubuntu/ trusty multiverse deb-src http://ca.archive.ubuntu.com/ubuntu/ trusty multiverse deb http://ca.archive.ubuntu.com/ubuntu/ trusty-updates multiverse deb-src http://ca.archive.ubuntu.com/ubuntu/ trusty-updates multiverse ## N.B. software from this repository may not have been tested as ## extensively as that contained in the main release, although it includes ## newer versions of some applications which may provide useful features. ## Also, please note that software in backports WILL NOT receive any review ## or updates from the Ubuntu security team. deb http://security.ubuntu.com/ubuntu trusty-security main restricted deb-src http://security.ubuntu.com/ubuntu trusty-security main restricted deb http://security.ubuntu.com/ubuntu trusty-security universe deb-src http://security.ubuntu.com/ubuntu trusty-security universe deb http://security.ubuntu.com/ubuntu trusty-security multiverse deb-src http://security.ubuntu.com/ubuntu trusty-security multiverse ## Uncomment the following two lines to add software from Canonical's ## 'partner' repository. ## This software is not part of Ubuntu, but is offered by Canonical and the ## respective vendors as a service to Ubuntu users. # deb http://archive.canonical.com/ubuntu raring partner # deb-src http://archive.canonical.com/ubuntu raring partner ## This software is not part of Ubuntu, but is offered by third-party ## developers who want to ship their latest software. deb http://extras.ubuntu.com/ubuntu trusty main
Re: [Desktop-packages] [Bug 1275908] Re: pkexec crashed with SIGABRT in g_assertion_message()
Tried to update software E:Type 'gksudo' is not known on line 1 in source list /etc/apt/sources.list.d/upubuntu-com-tor64-saucy.list, E:The list of sources could not be read., E:The package lists or status file could not be parsed or opened. On 10 February 2014 16:51, John Lozinska wrote: > E: Type 'gksudo' is not known on line 1 in source list > /etc/apt/sources.list.d/upubuntu-com-tor64-saucy.list > E: The list of sources could not be read. > videotron@videotron-Lenovo-B575:~$ gksudo apt-get upgrade > Reading package lists... Error! > videotron@videotron-Lenovo-B575:~$ gksudo apt-get upgrade > Reading package lists... Done > Building dependency tree > Reading state information... Done > Calculating upgrade... Done > The following packages were automatically installed and are no longer > required: > gir1.2-ibus-1.0 libgweather-3-3 libhud-client2 libpoppler43 libwebp4 > linux-headers-3.13.0-4 linux-headers-3.13.0-4-generic > linux-image-3.11.0-15-generic linux-image-3.13.0-4-generic > linux-image-extra-3.11.0-15-generic linux-image-extra-3.13.0-4-generic > Use 'apt-get autoremove' to remove them. > 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. > > When I did a previous action to access the sources list, it did come up as > shown below. I do not know what to do with that? > > # See http://help.ubuntu.com/community/UpgradeNotes for how to upgrade to > # newer versions of the distribution. > deb http://ca.archive.ubuntu.com/ubuntu/ trusty main restricted > deb-src http://ca.archive.ubuntu.com/ubuntu/ trusty main restricted > > ## Major bug fix updates produced after the final release of the > ## distribution. > deb http://ca.archive.ubuntu.com/ubuntu/ trusty-updates main restricted > deb-src http://ca.archive.ubuntu.com/ubuntu/ trusty-updates main > restricted > > ## N.B. software from this repository is ENTIRELY UNSUPPORTED by the Ubuntu > ## team. Also, please note that software in universe WILL NOT receive any > ## review or updates from the Ubuntu security team. > deb http://ca.archive.ubuntu.com/ubuntu/ trusty universe > deb-src http://ca.archive.ubuntu.com/ubuntu/ trusty universe > deb http://ca.archive.ubuntu.com/ubuntu/ trusty-updates universe > deb-src http://ca.archive.ubuntu.com/ubuntu/ trusty-updates universe > > ## N.B. software from this repository is ENTIRELY UNSUPPORTED by the > Ubuntu > ## team, and may not be under a free licence. Please satisfy yourself as > to > ## your rights to use the software. Also, please note that software in > ## multiverse WILL NOT receive any review or updates from the Ubuntu > ## security team. > deb http://ca.archive.ubuntu.com/ubuntu/ trusty multiverse > deb-src http://ca.archive.ubuntu.com/ubuntu/ trusty multiverse > deb http://ca.archive.ubuntu.com/ubuntu/ trusty-updates multiverse > deb-src http://ca.archive.ubuntu.com/ubuntu/ trusty-updates multiverse > > ## N.B. software from this repository may not have been tested as > ## extensively as that contained in the main release, although it includes > ## newer versions of some applications which may provide useful features. > ## Also, please note that software in backports WILL NOT receive any review > ## or updates from the Ubuntu security team. > > deb http://security.ubuntu.com/ubuntu trusty-security main restricted > deb-src http://security.ubuntu.com/ubuntu trusty-security main restricted > deb http://security.ubuntu.com/ubuntu trusty-security universe > deb-src http://security.ubuntu.com/ubuntu trusty-security universe > deb http://security.ubuntu.com/ubuntu trusty-security multiverse > deb-src http://security.ubuntu.com/ubuntu trusty-security multiverse > > ## Uncomment the following two lines to add software from Canonical's > ## 'partner' repository. > ## This software is not part of Ubuntu, but is offered by Canonical and the > ## respective vendors as a service to Ubuntu users. > # deb http://archive.canonical.com/ubuntu raring partner > # deb-src http://archive.canonical.com/ubuntu raring partner > > ## This software is not part of Ubuntu, but is offered by third-party > ## developers who want to ship their latest software. > deb http://extras.ubuntu.com/ubuntu trusty main > deb http://archive.canonical.com/ trusty partner > # deb-src http://archive.canonical.com/ raring partner > # deb-src http://archive.canonical.com/ raring partner > deb-src http://extras.ubuntu.com/ubuntu trusty main > deb http://ca.archive.ubuntu.com/ubuntu/ trusty-proposed restricted main > universe multiverse > deb http://www.duinsoft.nl/pkg debs all > > > > > > > On 10 February 2014 16:17, John Lozinska wrote: > >> Don't code and that is very confusing for me, brand new to Ubuntu. >> >> Tried /etc/apt/sources.list >> >> And got >> bash: /etc/apt/sources.list: Permission denied >> >> >> >> On 10 February 2014 15:20, Seth Arnold <1275...@bugs.launchpad.net>wrote: >> >>> For the 'gksudo' problem, edit your /etc/apt/sources.list.d/upubuntu- >>> com-tor64-saucy.list file and remove the 'gksudo' typo
Re: [Desktop-packages] [Bug 1275908] Re: pkexec crashed with SIGABRT in g_assertion_message()
My System says: Processor: AMD E-350 Processor × 2 Why x2? Normal? On 10 February 2014 17:02, John Lozinska wrote: > Tried to update software > > E:Type 'gksudo' is not known on line 1 in source list > /etc/apt/sources.list.d/upubuntu-com-tor64-saucy.list, E:The list of > sources could not be read., E:The package lists or status file could not be > parsed or opened. > > > On 10 February 2014 16:51, John Lozinska wrote: > >> E: Type 'gksudo' is not known on line 1 in source list >> /etc/apt/sources.list.d/upubuntu-com-tor64-saucy.list >> E: The list of sources could not be read. >> videotron@videotron-Lenovo-B575:~$ gksudo apt-get upgrade >> Reading package lists... Error! >> videotron@videotron-Lenovo-B575:~$ gksudo apt-get upgrade >> Reading package lists... Done >> Building dependency tree >> Reading state information... Done >> Calculating upgrade... Done >> The following packages were automatically installed and are no longer >> required: >> gir1.2-ibus-1.0 libgweather-3-3 libhud-client2 libpoppler43 libwebp4 >> linux-headers-3.13.0-4 linux-headers-3.13.0-4-generic >> linux-image-3.11.0-15-generic linux-image-3.13.0-4-generic >> linux-image-extra-3.11.0-15-generic linux-image-extra-3.13.0-4-generic >> Use 'apt-get autoremove' to remove them. >> 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. >> >> When I did a previous action to access the sources list, it did come up >> as shown below. I do not know what to do with that? >> >> # See http://help.ubuntu.com/community/UpgradeNotes for how to upgrade to >> # newer versions of the distribution. >> deb http://ca.archive.ubuntu.com/ubuntu/ trusty main restricted >> deb-src http://ca.archive.ubuntu.com/ubuntu/ trusty main restricted >> >> ## Major bug fix updates produced after the final release of the >> ## distribution. >> deb http://ca.archive.ubuntu.com/ubuntu/ trusty-updates main restricted >> deb-src http://ca.archive.ubuntu.com/ubuntu/ trusty-updates main >> restricted >> >> ## N.B. software from this repository is ENTIRELY UNSUPPORTED by the >> Ubuntu >> ## team. Also, please note that software in universe WILL NOT receive any >> ## review or updates from the Ubuntu security team. >> deb http://ca.archive.ubuntu.com/ubuntu/ trusty universe >> deb-src http://ca.archive.ubuntu.com/ubuntu/ trusty universe >> deb http://ca.archive.ubuntu.com/ubuntu/ trusty-updates universe >> deb-src http://ca.archive.ubuntu.com/ubuntu/ trusty-updates universe >> >> ## N.B. software from this repository is ENTIRELY UNSUPPORTED by the >> Ubuntu >> ## team, and may not be under a free licence. Please satisfy yourself as >> to >> ## your rights to use the software. Also, please note that software in >> ## multiverse WILL NOT receive any review or updates from the Ubuntu >> ## security team. >> deb http://ca.archive.ubuntu.com/ubuntu/ trusty multiverse >> deb-src http://ca.archive.ubuntu.com/ubuntu/ trusty multiverse >> deb http://ca.archive.ubuntu.com/ubuntu/ trusty-updates multiverse >> deb-src http://ca.archive.ubuntu.com/ubuntu/ trusty-updates multiverse >> >> ## N.B. software from this repository may not have been tested as >> ## extensively as that contained in the main release, although it includes >> ## newer versions of some applications which may provide useful features. >> ## Also, please note that software in backports WILL NOT receive any >> review >> ## or updates from the Ubuntu security team. >> >> deb http://security.ubuntu.com/ubuntu trusty-security main restricted >> deb-src http://security.ubuntu.com/ubuntu trusty-security main restricted >> deb http://security.ubuntu.com/ubuntu trusty-security universe >> deb-src http://security.ubuntu.com/ubuntu trusty-security universe >> deb http://security.ubuntu.com/ubuntu trusty-security multiverse >> deb-src http://security.ubuntu.com/ubuntu trusty-security multiverse >> >> ## Uncomment the following two lines to add software from Canonical's >> ## 'partner' repository. >> ## This software is not part of Ubuntu, but is offered by Canonical and >> the >> ## respective vendors as a service to Ubuntu users. >> # deb http://archive.canonical.com/ubuntu raring partner >> # deb-src http://archive.canonical.com/ubuntu raring partner >> >> ## This software is not part of Ubuntu, but is offered by third-party >> ## developers who want to ship their latest software. >> deb http://extras.ubuntu.com/ubuntu trusty main >> deb http://archive.canonical.com/ trusty partner >> # deb-src http://archive.canonical.com/ raring partner >> # deb-src http://archive.canonical.com/ raring partner >> deb-src http://extras.ubuntu.com/ubuntu trusty main >> deb http://ca.archive.ubuntu.com/ubuntu/ trusty-proposed restricted main >> universe multiverse >> deb http://www.duinsoft.nl/pkg debs all >> >> >> >> >> >> >> On 10 February 2014 16:17, John Lozinska wrote: >> >>> Don't code and that is very confusing for me, brand new to Ubuntu. >>> >>> Tried /etc/apt/sources.list >>> >>> And got >>> bash: /etc/apt/sources.
Re: [Desktop-packages] [Bug 1275908] Re: pkexec crashed with SIGABRT in g_assertion_message()
usr/bin/software-properties-gtk On 10 February 2014 17:03, John Lozinska wrote: > My System says: > > Processor: AMD E-350 Processor × 2 > > Why x2? Normal? > > > > On 10 February 2014 17:02, John Lozinska wrote: > >> Tried to update software >> >> E:Type 'gksudo' is not known on line 1 in source list >> /etc/apt/sources.list.d/upubuntu-com-tor64-saucy.list, E:The list of >> sources could not be read., E:The package lists or status file could not be >> parsed or opened. >> >> >> On 10 February 2014 16:51, John Lozinska wrote: >> >>> E: Type 'gksudo' is not known on line 1 in source list >>> /etc/apt/sources.list.d/upubuntu-com-tor64-saucy.list >>> E: The list of sources could not be read. >>> videotron@videotron-Lenovo-B575:~$ gksudo apt-get upgrade >>> Reading package lists... Error! >>> videotron@videotron-Lenovo-B575:~$ gksudo apt-get upgrade >>> Reading package lists... Done >>> Building dependency tree >>> Reading state information... Done >>> Calculating upgrade... Done >>> The following packages were automatically installed and are no longer >>> required: >>> gir1.2-ibus-1.0 libgweather-3-3 libhud-client2 libpoppler43 libwebp4 >>> linux-headers-3.13.0-4 linux-headers-3.13.0-4-generic >>> linux-image-3.11.0-15-generic linux-image-3.13.0-4-generic >>> linux-image-extra-3.11.0-15-generic linux-image-extra-3.13.0-4-generic >>> Use 'apt-get autoremove' to remove them. >>> 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. >>> >>> When I did a previous action to access the sources list, it did come up >>> as shown below. I do not know what to do with that? >>> >>> # See http://help.ubuntu.com/community/UpgradeNotes for how to upgrade >>> to >>> # newer versions of the distribution. >>> deb http://ca.archive.ubuntu.com/ubuntu/ trusty main restricted >>> deb-src http://ca.archive.ubuntu.com/ubuntu/ trusty main restricted >>> >>> ## Major bug fix updates produced after the final release of the >>> ## distribution. >>> deb http://ca.archive.ubuntu.com/ubuntu/ trusty-updates main restricted >>> deb-src http://ca.archive.ubuntu.com/ubuntu/ trusty-updates main >>> restricted >>> >>> ## N.B. software from this repository is ENTIRELY UNSUPPORTED by the >>> Ubuntu >>> ## team. Also, please note that software in universe WILL NOT receive any >>> ## review or updates from the Ubuntu security team. >>> deb http://ca.archive.ubuntu.com/ubuntu/ trusty universe >>> deb-src http://ca.archive.ubuntu.com/ubuntu/ trusty universe >>> deb http://ca.archive.ubuntu.com/ubuntu/ trusty-updates universe >>> deb-src http://ca.archive.ubuntu.com/ubuntu/ trusty-updates universe >>> >>> ## N.B. software from this repository is ENTIRELY UNSUPPORTED by the >>> Ubuntu >>> ## team, and may not be under a free licence. Please satisfy yourself as >>> to >>> ## your rights to use the software. Also, please note that software in >>> ## multiverse WILL NOT receive any review or updates from the Ubuntu >>> ## security team. >>> deb http://ca.archive.ubuntu.com/ubuntu/ trusty multiverse >>> deb-src http://ca.archive.ubuntu.com/ubuntu/ trusty multiverse >>> deb http://ca.archive.ubuntu.com/ubuntu/ trusty-updates multiverse >>> deb-src http://ca.archive.ubuntu.com/ubuntu/ trusty-updates multiverse >>> >>> ## N.B. software from this repository may not have been tested as >>> ## extensively as that contained in the main release, although it >>> includes >>> ## newer versions of some applications which may provide useful features. >>> ## Also, please note that software in backports WILL NOT receive any >>> review >>> ## or updates from the Ubuntu security team. >>> >>> deb http://security.ubuntu.com/ubuntu trusty-security main restricted >>> deb-src http://security.ubuntu.com/ubuntu trusty-security main >>> restricted >>> deb http://security.ubuntu.com/ubuntu trusty-security universe >>> deb-src http://security.ubuntu.com/ubuntu trusty-security universe >>> deb http://security.ubuntu.com/ubuntu trusty-security multiverse >>> deb-src http://security.ubuntu.com/ubuntu trusty-security multiverse >>> >>> ## Uncomment the following two lines to add software from Canonical's >>> ## 'partner' repository. >>> ## This software is not part of Ubuntu, but is offered by Canonical and >>> the >>> ## respective vendors as a service to Ubuntu users. >>> # deb http://archive.canonical.com/ubuntu raring partner >>> # deb-src http://archive.canonical.com/ubuntu raring partner >>> >>> ## This software is not part of Ubuntu, but is offered by third-party >>> ## developers who want to ship their latest software. >>> deb http://extras.ubuntu.com/ubuntu trusty main >>> deb http://archive.canonical.com/ trusty partner >>> # deb-src http://archive.canonical.com/ raring partner >>> # deb-src http://archive.canonical.com/ raring partner >>> deb-src http://extras.ubuntu.com/ubuntu trusty main >>> deb http://ca.archive.ubuntu.com/ubuntu/ trusty-proposed restricted >>> main universe multiverse >>> deb http://www.duinsoft.nl/pkg debs all >>> >>> >>> >>>
Re: [Desktop-packages] [Bug 1275908] Re: pkexec crashed with SIGABRT in g_assertion_message()
E: Type 'gksudo' is not known on line 1 in source list /etc/apt/sources.list.d/upubuntu-com-tor64-saucy.list E: The list of sources could not be read. videotron@videotron-Lenovo-B575:~$ gksudo apt-get upgrade Reading package lists... Error! videotron@videotron-Lenovo-B575:~$ gksudo apt-get upgrade Reading package lists... Done Building dependency tree Reading state information... Done Calculating upgrade... Done The following packages were automatically installed and are no longer required: gir1.2-ibus-1.0 libgweather-3-3 libhud-client2 libpoppler43 libwebp4 linux-headers-3.13.0-4 linux-headers-3.13.0-4-generic linux-image-3.11.0-15-generic linux-image-3.13.0-4-generic linux-image-extra-3.11.0-15-generic linux-image-extra-3.13.0-4-generic Use 'apt-get autoremove' to remove them. 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. When I did a previous action to access the sources list, it did come up as shown below. I do not know what to do with that? # See http://help.ubuntu.com/community/UpgradeNotes for how to upgrade to # newer versions of the distribution. deb http://ca.archive.ubuntu.com/ubuntu/ trusty main restricted deb-src http://ca.archive.ubuntu.com/ubuntu/ trusty main restricted ## Major bug fix updates produced after the final release of the ## distribution. deb http://ca.archive.ubuntu.com/ubuntu/ trusty-updates main restricted deb-src http://ca.archive.ubuntu.com/ubuntu/ trusty-updates main restricted ## N.B. software from this repository is ENTIRELY UNSUPPORTED by the Ubuntu ## team. Also, please note that software in universe WILL NOT receive any ## review or updates from the Ubuntu security team. deb http://ca.archive.ubuntu.com/ubuntu/ trusty universe deb-src http://ca.archive.ubuntu.com/ubuntu/ trusty universe deb http://ca.archive.ubuntu.com/ubuntu/ trusty-updates universe deb-src http://ca.archive.ubuntu.com/ubuntu/ trusty-updates universe ## N.B. software from this repository is ENTIRELY UNSUPPORTED by the Ubuntu ## team, and may not be under a free licence. Please satisfy yourself as to ## your rights to use the software. Also, please note that software in ## multiverse WILL NOT receive any review or updates from the Ubuntu ## security team. deb http://ca.archive.ubuntu.com/ubuntu/ trusty multiverse deb-src http://ca.archive.ubuntu.com/ubuntu/ trusty multiverse deb http://ca.archive.ubuntu.com/ubuntu/ trusty-updates multiverse deb-src http://ca.archive.ubuntu.com/ubuntu/ trusty-updates multiverse ## N.B. software from this repository may not have been tested as ## extensively as that contained in the main release, although it includes ## newer versions of some applications which may provide useful features. ## Also, please note that software in backports WILL NOT receive any review ## or updates from the Ubuntu security team. deb http://security.ubuntu.com/ubuntu trusty-security main restricted deb-src http://security.ubuntu.com/ubuntu trusty-security main restricted deb http://security.ubuntu.com/ubuntu trusty-security universe deb-src http://security.ubuntu.com/ubuntu trusty-security universe deb http://security.ubuntu.com/ubuntu trusty-security multiverse deb-src http://security.ubuntu.com/ubuntu trusty-security multiverse ## Uncomment the following two lines to add software from Canonical's ## 'partner' repository. ## This software is not part of Ubuntu, but is offered by Canonical and the ## respective vendors as a service to Ubuntu users. # deb http://archive.canonical.com/ubuntu raring partner # deb-src http://archive.canonical.com/ubuntu raring partner ## This software is not part of Ubuntu, but is offered by third-party ## developers who want to ship their latest software. deb http://extras.ubuntu.com/ubuntu trusty main deb http://archive.canonical.com/ trusty partner # deb-src http://archive.canonical.com/ raring partner # deb-src http://archive.canonical.com/ raring partner deb-src http://extras.ubuntu.com/ubuntu trusty main deb http://ca.archive.ubuntu.com/ubuntu/ trusty-proposed restricted main universe multiverse deb http://www.duinsoft.nl/pkg debs all On 10 February 2014 16:17, John Lozinska wrote: > Don't code and that is very confusing for me, brand new to Ubuntu. > > Tried /etc/apt/sources.list > > And got > bash: /etc/apt/sources.list: Permission denied > > > > On 10 February 2014 15:20, Seth Arnold <1275...@bugs.launchpad.net> wrote: > >> For the 'gksudo' problem, edit your /etc/apt/sources.list.d/upubuntu- >> com-tor64-saucy.list file and remove the 'gksudo' typo. See the >> sources.list(5) manpage for details on the correct format of the apt >> sources files: >> >> man 5 sources.list >> >> Thanks >> >> -- >> You received this bug notification because you are subscribed to the bug >> report. >> https://bugs.launchpad.net/bugs/1275908 >> >> Title: >> pkexec crashed with SIGABRT in g_assertion_message() >> >> Status in "policykit-1" package in Ubuntu: >> Invalid >> >> Bug description: >> No more info to offer. >> >> Proble
Re: [Desktop-packages] [Bug 1275908] Re: pkexec crashed with SIGABRT in g_assertion_message()
Don't code and that is very confusing for me, brand new to Ubuntu. Tried /etc/apt/sources.list And got bash: /etc/apt/sources.list: Permission denied On 10 February 2014 15:20, Seth Arnold <1275...@bugs.launchpad.net> wrote: > For the 'gksudo' problem, edit your /etc/apt/sources.list.d/upubuntu- > com-tor64-saucy.list file and remove the 'gksudo' typo. See the > sources.list(5) manpage for details on the correct format of the apt > sources files: > > man 5 sources.list > > Thanks > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1275908 > > Title: > pkexec crashed with SIGABRT in g_assertion_message() > > Status in "policykit-1" package in Ubuntu: > Invalid > > Bug description: > No more info to offer. > > ProblemType: Crash > DistroRelease: Ubuntu 14.04 > Package: policykit-1 0.105-4ubuntu1 > ProcVersionSignature: Ubuntu 3.13.0-6.23-generic 3.13.0 > Uname: Linux 3.13.0-6-generic i686 > ApportVersion: 2.13.2-0ubuntu2 > Architecture: i386 > CrashCounter: 1 > CurrentDesktop: Unity > Date: Mon Feb 3 14:17:47 2014 > ExecutablePath: /usr/bin/pkexec > InstallationDate: Installed on 2014-01-11 (23 days ago) > InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release i386 > (20130424) > ProcAttrCurrent: /usr/lib/lightdm/lightdm-guest-session (enforce) > ProcCmdline: pkexec /usr/lib/gnome-settings-daemon/gsd-backlight-helper > --set-brightness 3 > ProcEnviron: >PATH=(custom, no user) >LANGUAGE=en_CA:en >XDG_RUNTIME_DIR= >LANG=en_CA.UTF-8 >SHELL=/bin/bash > Signal: 6 > SourcePackage: policykit-1 > StacktraceTop: >g_assertion_message () from /lib/i386-linux-gnu/libglib-2.0.so.0 >g_assertion_message_expr () from /lib/i386-linux-gnu/libglib-2.0.so.0 >?? () >__libc_start_main (main=0x80497f0, argc=4, argv=0xbf9de964, > init=0x804b0a0, fini=0x804b110, rtld_fini=0xb776c0f0 <_dl_fini>, > stack_end=0xbf9de95c) at libc-start.c:287 >?? () > Title: pkexec crashed with SIGABRT in g_assertion_message() > UpgradeStatus: Upgraded to trusty on 2014-01-18 (16 days ago) > UserGroups: > > To manage notifications about this bug go to: > > https://bugs.launchpad.net/ubuntu/+source/policykit-1/+bug/1275908/+subscriptions > -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to policykit-1 in Ubuntu. https://bugs.launchpad.net/bugs/1275908 Title: pkexec crashed with SIGABRT in g_assertion_message() Status in “policykit-1” package in Ubuntu: Invalid Bug description: No more info to offer. ProblemType: Crash DistroRelease: Ubuntu 14.04 Package: policykit-1 0.105-4ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-6.23-generic 3.13.0 Uname: Linux 3.13.0-6-generic i686 ApportVersion: 2.13.2-0ubuntu2 Architecture: i386 CrashCounter: 1 CurrentDesktop: Unity Date: Mon Feb 3 14:17:47 2014 ExecutablePath: /usr/bin/pkexec InstallationDate: Installed on 2014-01-11 (23 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release i386 (20130424) ProcAttrCurrent: /usr/lib/lightdm/lightdm-guest-session (enforce) ProcCmdline: pkexec /usr/lib/gnome-settings-daemon/gsd-backlight-helper --set-brightness 3 ProcEnviron: PATH=(custom, no user) LANGUAGE=en_CA:en XDG_RUNTIME_DIR= LANG=en_CA.UTF-8 SHELL=/bin/bash Signal: 6 SourcePackage: policykit-1 StacktraceTop: g_assertion_message () from /lib/i386-linux-gnu/libglib-2.0.so.0 g_assertion_message_expr () from /lib/i386-linux-gnu/libglib-2.0.so.0 ?? () __libc_start_main (main=0x80497f0, argc=4, argv=0xbf9de964, init=0x804b0a0, fini=0x804b110, rtld_fini=0xb776c0f0 <_dl_fini>, stack_end=0xbf9de95c) at libc-start.c:287 ?? () Title: pkexec crashed with SIGABRT in g_assertion_message() UpgradeStatus: Upgraded to trusty on 2014-01-18 (16 days ago) UserGroups: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/policykit-1/+bug/1275908/+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 1181902] Re: Nouveau driver glitch on Ubuntu 13.04 will cause system to freeze under certain conditions
BTW, found another reference for this issue: https://bugs.freedesktop.org/show_bug.cgi?id=72458 ** Bug watch added: freedesktop.org Bugzilla #72458 https://bugs.freedesktop.org/show_bug.cgi?id=72458 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-video-nouveau in Ubuntu. https://bugs.launchpad.net/bugs/1181902 Title: Nouveau driver glitch on Ubuntu 13.04 will cause system to freeze under certain conditions Status in “xserver-xorg-video-nouveau” package in Ubuntu: Incomplete Bug description: Hi, This only happens to Ubuntu 13.04, as my GeForce 6150SE card was working fine for Ubuntu 12.10. The Nouveau driver glitch will cause my whole system to freeze under certain conditions. I first get my system freeze when starting virtualbox, which is installed from the offical Oracle virtualbox PPA. Duplicated several times -- Freshly boot into X, then start virtualbox from within xterm via "virtualbox &", 2 seconds later my whole system freeze up. Google search indicated that it might be cause by the offical Oracle virtualbox PPA, so I followed the advice to switch to the offical Ubuntu virtualbox from the software center, but get into system freeze doing exactly the same thing. Duplicated several times as well. I was about to conclude that it is the virtualbox's problem when I suddenly remember that I've got into such system freeze before doing something entirely different, because the symptom is exactly the same. So I tried again -- "startx -- :1" to get me into another X session, and quit. Yes, then and there, I get into such system freeze again. The symptom is that the display turned black, then a random pattern tiled across the whole screen. Installing the closed source additional driver (nvidia) to replace the Nouveau driver solve the problem, which in turn proved that my suspicion was right -- it *is* the Nouveau driver that is causing the problem. Thanks PS. Comparing with the previous Xorg.1.log, the lines that didn't get output are: (II) NOUVEAU(0): EDID vendor "ACR", prod id 426 (II) NOUVEAU(0): Using EDID range info for horizontal sync (II) NOUVEAU(0): Using EDID range info for vertical refresh (II) NOUVEAU(0): Printing DDC gathered Modelines: . . . The whole unloading part (filtered by "sed 's/\[[^]]*]//'") of my previous Xorg.1.log is at http://paste.debian.net/5260/, the whole un- filtered file is at http://paste.debian.net/5261/. Here is my GeForce 6150SE card: $ lspci | grep VGA 00:0d.0 VGA compatible controller: NVIDIA Corporation C61 [GeForce 6150SE nForce 430] (rev a2) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-nouveau/+bug/1181902/+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 1181902] Re: Nouveau driver glitch on Ubuntu 13.04 will cause system to freeze under certain conditions
Christopher, I downloaded today's ISO from dev-branch, but it was impossible to complete the command: apport-collect -p xserver-xorg-video-nouveau 1181902 because I can't even start Ubuntu from graphic mode. When I click on "Preview Ubuntu" (rather than Install) I switched shell (Ctrl + Alt + F2) and noticed the following message: [ 307.xxx.xxx] nouveau e [ PBUS] [:00:0d.0] MMIO write of 0x FAULT at 0x00b010 and then, the system goes laggy as hell... Super slow-mo. Seriously. Back to graphical mode (Ctrl + Alt + F7), moved the mouse and cursor position refreshed after 10 secs. Same thing to keyboard response. Then: System freezes. apport-collect needs response from browser... So, I'm sorry. This bug makes this impossible. Can I attach some other information without using browser or graphical mode with dev-ISO? I really miss Ubuntu in my computer! :( -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-video-nouveau in Ubuntu. https://bugs.launchpad.net/bugs/1181902 Title: Nouveau driver glitch on Ubuntu 13.04 will cause system to freeze under certain conditions Status in “xserver-xorg-video-nouveau” package in Ubuntu: Incomplete Bug description: Hi, This only happens to Ubuntu 13.04, as my GeForce 6150SE card was working fine for Ubuntu 12.10. The Nouveau driver glitch will cause my whole system to freeze under certain conditions. I first get my system freeze when starting virtualbox, which is installed from the offical Oracle virtualbox PPA. Duplicated several times -- Freshly boot into X, then start virtualbox from within xterm via "virtualbox &", 2 seconds later my whole system freeze up. Google search indicated that it might be cause by the offical Oracle virtualbox PPA, so I followed the advice to switch to the offical Ubuntu virtualbox from the software center, but get into system freeze doing exactly the same thing. Duplicated several times as well. I was about to conclude that it is the virtualbox's problem when I suddenly remember that I've got into such system freeze before doing something entirely different, because the symptom is exactly the same. So I tried again -- "startx -- :1" to get me into another X session, and quit. Yes, then and there, I get into such system freeze again. The symptom is that the display turned black, then a random pattern tiled across the whole screen. Installing the closed source additional driver (nvidia) to replace the Nouveau driver solve the problem, which in turn proved that my suspicion was right -- it *is* the Nouveau driver that is causing the problem. Thanks PS. Comparing with the previous Xorg.1.log, the lines that didn't get output are: (II) NOUVEAU(0): EDID vendor "ACR", prod id 426 (II) NOUVEAU(0): Using EDID range info for horizontal sync (II) NOUVEAU(0): Using EDID range info for vertical refresh (II) NOUVEAU(0): Printing DDC gathered Modelines: . . . The whole unloading part (filtered by "sed 's/\[[^]]*]//'") of my previous Xorg.1.log is at http://paste.debian.net/5260/, the whole un- filtered file is at http://paste.debian.net/5261/. Here is my GeForce 6150SE card: $ lspci | grep VGA 00:0d.0 VGA compatible controller: NVIDIA Corporation C61 [GeForce 6150SE nForce 430] (rev a2) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-nouveau/+bug/1181902/+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 1275908] Re: pkexec crashed with SIGABRT in g_assertion_message()
Thanks, I will try that. Before I try that, I will say I ran gksudo for some dumb reason and messed up the system E:Type 'gksudo' is not known on line 1 in source list /etc/apt/sources.list.d/upubuntu-com-tor64-saucy.list I will try that now, thanks! Allan On 7 February 2014 14:27, Seth Arnold <1275...@bugs.launchpad.net> wrote: > Try this in a terminal: > > sudo apt-get update && sudo apt-get -u dist-upgrade > > If you get any error messages, please post them here. > > Thanks > > ** Information type changed from Private Security to Public > > ** Information type changed from Public to Public Security > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1275908 > > Title: > pkexec crashed with SIGABRT in g_assertion_message() > > Status in "policykit-1" package in Ubuntu: > Invalid > > Bug description: > No more info to offer. > > ProblemType: Crash > DistroRelease: Ubuntu 14.04 > Package: policykit-1 0.105-4ubuntu1 > ProcVersionSignature: Ubuntu 3.13.0-6.23-generic 3.13.0 > Uname: Linux 3.13.0-6-generic i686 > ApportVersion: 2.13.2-0ubuntu2 > Architecture: i386 > CrashCounter: 1 > CurrentDesktop: Unity > Date: Mon Feb 3 14:17:47 2014 > ExecutablePath: /usr/bin/pkexec > InstallationDate: Installed on 2014-01-11 (23 days ago) > InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release i386 > (20130424) > ProcAttrCurrent: /usr/lib/lightdm/lightdm-guest-session (enforce) > ProcCmdline: pkexec /usr/lib/gnome-settings-daemon/gsd-backlight-helper > --set-brightness 3 > ProcEnviron: >PATH=(custom, no user) >LANGUAGE=en_CA:en >XDG_RUNTIME_DIR= >LANG=en_CA.UTF-8 >SHELL=/bin/bash > Signal: 6 > SourcePackage: policykit-1 > StacktraceTop: >g_assertion_message () from /lib/i386-linux-gnu/libglib-2.0.so.0 >g_assertion_message_expr () from /lib/i386-linux-gnu/libglib-2.0.so.0 >?? () >__libc_start_main (main=0x80497f0, argc=4, argv=0xbf9de964, > init=0x804b0a0, fini=0x804b110, rtld_fini=0xb776c0f0 <_dl_fini>, > stack_end=0xbf9de95c) at libc-start.c:287 >?? () > Title: pkexec crashed with SIGABRT in g_assertion_message() > UpgradeStatus: Upgraded to trusty on 2014-01-18 (16 days ago) > UserGroups: > > To manage notifications about this bug go to: > > https://bugs.launchpad.net/ubuntu/+source/policykit-1/+bug/1275908/+subscriptions > -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to policykit-1 in Ubuntu. https://bugs.launchpad.net/bugs/1275908 Title: pkexec crashed with SIGABRT in g_assertion_message() Status in “policykit-1” package in Ubuntu: Invalid Bug description: No more info to offer. ProblemType: Crash DistroRelease: Ubuntu 14.04 Package: policykit-1 0.105-4ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-6.23-generic 3.13.0 Uname: Linux 3.13.0-6-generic i686 ApportVersion: 2.13.2-0ubuntu2 Architecture: i386 CrashCounter: 1 CurrentDesktop: Unity Date: Mon Feb 3 14:17:47 2014 ExecutablePath: /usr/bin/pkexec InstallationDate: Installed on 2014-01-11 (23 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release i386 (20130424) ProcAttrCurrent: /usr/lib/lightdm/lightdm-guest-session (enforce) ProcCmdline: pkexec /usr/lib/gnome-settings-daemon/gsd-backlight-helper --set-brightness 3 ProcEnviron: PATH=(custom, no user) LANGUAGE=en_CA:en XDG_RUNTIME_DIR= LANG=en_CA.UTF-8 SHELL=/bin/bash Signal: 6 SourcePackage: policykit-1 StacktraceTop: g_assertion_message () from /lib/i386-linux-gnu/libglib-2.0.so.0 g_assertion_message_expr () from /lib/i386-linux-gnu/libglib-2.0.so.0 ?? () __libc_start_main (main=0x80497f0, argc=4, argv=0xbf9de964, init=0x804b0a0, fini=0x804b110, rtld_fini=0xb776c0f0 <_dl_fini>, stack_end=0xbf9de95c) at libc-start.c:287 ?? () Title: pkexec crashed with SIGABRT in g_assertion_message() UpgradeStatus: Upgraded to trusty on 2014-01-18 (16 days ago) UserGroups: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/policykit-1/+bug/1275908/+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 1275908] Re: pkexec crashed with SIGABRT in g_assertion_message()
Pretty sure I have 32bit, not 64 also. On 8 February 2014 03:24, Allan Nott wrote: > The message above. ;) > > E: Type 'gksudo' is not known on line 1 in source list > /etc/apt/sources.list.d/upubuntu-com-tor64-saucy.list > > > > On 8 February 2014 03:22, Allan Nott wrote: > >> Thanks, I will try that. >> >> Before I try that, I will say I ran gksudo for some dumb reason and >> messed up the system >> >> E:Type 'gksudo' is not known on line 1 in source list >> /etc/apt/sources.list.d/upubuntu-com-tor64-saucy.list >> >> I will try that now, thanks! >> >> Allan >> >> >> On 7 February 2014 14:27, Seth Arnold <1275...@bugs.launchpad.net> wrote: >> >>> Try this in a terminal: >>> >>> sudo apt-get update && sudo apt-get -u dist-upgrade >>> >>> If you get any error messages, please post them here. >>> >>> Thanks >>> >>> ** Information type changed from Private Security to Public >>> >>> ** Information type changed from Public to Public Security >>> >>> -- >>> You received this bug notification because you are subscribed to the bug >>> report. >>> https://bugs.launchpad.net/bugs/1275908 >>> >>> Title: >>> pkexec crashed with SIGABRT in g_assertion_message() >>> >>> Status in "policykit-1" package in Ubuntu: >>> Invalid >>> >>> Bug description: >>> No more info to offer. >>> >>> ProblemType: Crash >>> DistroRelease: Ubuntu 14.04 >>> Package: policykit-1 0.105-4ubuntu1 >>> ProcVersionSignature: Ubuntu 3.13.0-6.23-generic 3.13.0 >>> Uname: Linux 3.13.0-6-generic i686 >>> ApportVersion: 2.13.2-0ubuntu2 >>> Architecture: i386 >>> CrashCounter: 1 >>> CurrentDesktop: Unity >>> Date: Mon Feb 3 14:17:47 2014 >>> ExecutablePath: /usr/bin/pkexec >>> InstallationDate: Installed on 2014-01-11 (23 days ago) >>> InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release i386 >>> (20130424) >>> ProcAttrCurrent: /usr/lib/lightdm/lightdm-guest-session (enforce) >>> ProcCmdline: pkexec >>> /usr/lib/gnome-settings-daemon/gsd-backlight-helper --set-brightness 3 >>> ProcEnviron: >>>PATH=(custom, no user) >>>LANGUAGE=en_CA:en >>>XDG_RUNTIME_DIR= >>>LANG=en_CA.UTF-8 >>>SHELL=/bin/bash >>> Signal: 6 >>> SourcePackage: policykit-1 >>> StacktraceTop: >>>g_assertion_message () from /lib/i386-linux-gnu/libglib-2.0.so.0 >>>g_assertion_message_expr () from /lib/i386-linux-gnu/libglib-2.0.so.0 >>>?? () >>>__libc_start_main (main=0x80497f0, argc=4, argv=0xbf9de964, >>> init=0x804b0a0, fini=0x804b110, rtld_fini=0xb776c0f0 <_dl_fini>, >>> stack_end=0xbf9de95c) at libc-start.c:287 >>>?? () >>> Title: pkexec crashed with SIGABRT in g_assertion_message() >>> UpgradeStatus: Upgraded to trusty on 2014-01-18 (16 days ago) >>> UserGroups: >>> >>> To manage notifications about this bug go to: >>> >>> https://bugs.launchpad.net/ubuntu/+source/policykit-1/+bug/1275908/+subscriptions >>> >> >> > -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to policykit-1 in Ubuntu. https://bugs.launchpad.net/bugs/1275908 Title: pkexec crashed with SIGABRT in g_assertion_message() Status in “policykit-1” package in Ubuntu: Invalid Bug description: No more info to offer. ProblemType: Crash DistroRelease: Ubuntu 14.04 Package: policykit-1 0.105-4ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-6.23-generic 3.13.0 Uname: Linux 3.13.0-6-generic i686 ApportVersion: 2.13.2-0ubuntu2 Architecture: i386 CrashCounter: 1 CurrentDesktop: Unity Date: Mon Feb 3 14:17:47 2014 ExecutablePath: /usr/bin/pkexec InstallationDate: Installed on 2014-01-11 (23 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release i386 (20130424) ProcAttrCurrent: /usr/lib/lightdm/lightdm-guest-session (enforce) ProcCmdline: pkexec /usr/lib/gnome-settings-daemon/gsd-backlight-helper --set-brightness 3 ProcEnviron: PATH=(custom, no user) LANGUAGE=en_CA:en XDG_RUNTIME_DIR= LANG=en_CA.UTF-8 SHELL=/bin/bash Signal: 6 SourcePackage: policykit-1 StacktraceTop: g_assertion_message () from /lib/i386-linux-gnu/libglib-2.0.so.0 g_assertion_message_expr () from /lib/i386-linux-gnu/libglib-2.0.so.0 ?? () __libc_start_main (main=0x80497f0, argc=4, argv=0xbf9de964, init=0x804b0a0, fini=0x804b110, rtld_fini=0xb776c0f0 <_dl_fini>, stack_end=0xbf9de95c) at libc-start.c:287 ?? () Title: pkexec crashed with SIGABRT in g_assertion_message() UpgradeStatus: Upgraded to trusty on 2014-01-18 (16 days ago) UserGroups: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/policykit-1/+bug/1275908/+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 1275908] Re: pkexec crashed with SIGABRT in g_assertion_message()
The message above. ;) E: Type 'gksudo' is not known on line 1 in source list /etc/apt/sources.list.d/upubuntu-com-tor64-saucy.list On 8 February 2014 03:22, Allan Nott wrote: > Thanks, I will try that. > > Before I try that, I will say I ran gksudo for some dumb reason and messed > up the system > > E:Type 'gksudo' is not known on line 1 in source list > /etc/apt/sources.list.d/upubuntu-com-tor64-saucy.list > > I will try that now, thanks! > > Allan > > > On 7 February 2014 14:27, Seth Arnold <1275...@bugs.launchpad.net> wrote: > >> Try this in a terminal: >> >> sudo apt-get update && sudo apt-get -u dist-upgrade >> >> If you get any error messages, please post them here. >> >> Thanks >> >> ** Information type changed from Private Security to Public >> >> ** Information type changed from Public to Public Security >> >> -- >> You received this bug notification because you are subscribed to the bug >> report. >> https://bugs.launchpad.net/bugs/1275908 >> >> Title: >> pkexec crashed with SIGABRT in g_assertion_message() >> >> Status in "policykit-1" package in Ubuntu: >> Invalid >> >> Bug description: >> No more info to offer. >> >> ProblemType: Crash >> DistroRelease: Ubuntu 14.04 >> Package: policykit-1 0.105-4ubuntu1 >> ProcVersionSignature: Ubuntu 3.13.0-6.23-generic 3.13.0 >> Uname: Linux 3.13.0-6-generic i686 >> ApportVersion: 2.13.2-0ubuntu2 >> Architecture: i386 >> CrashCounter: 1 >> CurrentDesktop: Unity >> Date: Mon Feb 3 14:17:47 2014 >> ExecutablePath: /usr/bin/pkexec >> InstallationDate: Installed on 2014-01-11 (23 days ago) >> InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release i386 >> (20130424) >> ProcAttrCurrent: /usr/lib/lightdm/lightdm-guest-session (enforce) >> ProcCmdline: pkexec /usr/lib/gnome-settings-daemon/gsd-backlight-helper >> --set-brightness 3 >> ProcEnviron: >>PATH=(custom, no user) >>LANGUAGE=en_CA:en >>XDG_RUNTIME_DIR= >>LANG=en_CA.UTF-8 >>SHELL=/bin/bash >> Signal: 6 >> SourcePackage: policykit-1 >> StacktraceTop: >>g_assertion_message () from /lib/i386-linux-gnu/libglib-2.0.so.0 >>g_assertion_message_expr () from /lib/i386-linux-gnu/libglib-2.0.so.0 >>?? () >>__libc_start_main (main=0x80497f0, argc=4, argv=0xbf9de964, >> init=0x804b0a0, fini=0x804b110, rtld_fini=0xb776c0f0 <_dl_fini>, >> stack_end=0xbf9de95c) at libc-start.c:287 >>?? () >> Title: pkexec crashed with SIGABRT in g_assertion_message() >> UpgradeStatus: Upgraded to trusty on 2014-01-18 (16 days ago) >> UserGroups: >> >> To manage notifications about this bug go to: >> >> https://bugs.launchpad.net/ubuntu/+source/policykit-1/+bug/1275908/+subscriptions >> > > -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to policykit-1 in Ubuntu. https://bugs.launchpad.net/bugs/1275908 Title: pkexec crashed with SIGABRT in g_assertion_message() Status in “policykit-1” package in Ubuntu: Invalid Bug description: No more info to offer. ProblemType: Crash DistroRelease: Ubuntu 14.04 Package: policykit-1 0.105-4ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-6.23-generic 3.13.0 Uname: Linux 3.13.0-6-generic i686 ApportVersion: 2.13.2-0ubuntu2 Architecture: i386 CrashCounter: 1 CurrentDesktop: Unity Date: Mon Feb 3 14:17:47 2014 ExecutablePath: /usr/bin/pkexec InstallationDate: Installed on 2014-01-11 (23 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release i386 (20130424) ProcAttrCurrent: /usr/lib/lightdm/lightdm-guest-session (enforce) ProcCmdline: pkexec /usr/lib/gnome-settings-daemon/gsd-backlight-helper --set-brightness 3 ProcEnviron: PATH=(custom, no user) LANGUAGE=en_CA:en XDG_RUNTIME_DIR= LANG=en_CA.UTF-8 SHELL=/bin/bash Signal: 6 SourcePackage: policykit-1 StacktraceTop: g_assertion_message () from /lib/i386-linux-gnu/libglib-2.0.so.0 g_assertion_message_expr () from /lib/i386-linux-gnu/libglib-2.0.so.0 ?? () __libc_start_main (main=0x80497f0, argc=4, argv=0xbf9de964, init=0x804b0a0, fini=0x804b110, rtld_fini=0xb776c0f0 <_dl_fini>, stack_end=0xbf9de95c) at libc-start.c:287 ?? () Title: pkexec crashed with SIGABRT in g_assertion_message() UpgradeStatus: Upgraded to trusty on 2014-01-18 (16 days ago) UserGroups: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/policykit-1/+bug/1275908/+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 1276380] [NEW] [HP Pavilion g4 Notebook PC, IDT 92HD87B2/4, Speaker, Internal] No sound at all
Public bug reported: m4p archive dont work ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: alsa-base 1.0.25+dfsg-0ubuntu4 ProcVersionSignature: Ubuntu 3.11.0-15.25-generic 3.11.10 Uname: Linux 3.11.0-15-generic x86_64 ApportVersion: 2.12.5-0ubuntu2.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: atriminio 1886 F pulseaudio /dev/snd/controlC0: atriminio 1886 F pulseaudio Date: Tue Feb 4 18:38:42 2014 InstallationDate: Installed on 2014-01-28 (7 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) MarkForUpload: True PackageArchitecture: all ProcEnviron: LANGUAGE=es_HN:es PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=es_HN.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Generic successful Symptom_Card: Audio Interno - HD-Audio Generic Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: atriminio 1886 F pulseaudio /dev/snd/controlC0: atriminio 1886 F pulseaudio Symptom_Jack: Speaker, Internal Symptom_PulsePlaybackTest: PulseAudio playback test successful Symptom_Type: No sound at all Title: [HP Pavilion g4 Notebook PC, IDT 92HD87B2/4, Speaker, Internal] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/12/2013 dmi.bios.vendor: Insyde dmi.bios.version: F.27 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 1847 dmi.board.vendor: Hewlett-Packard dmi.board.version: 57.35 dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.27:bd04/12/2013:svnHewlett-Packard:pnHPPaviliong4NotebookPC:pvr088212305B1610100:rvnHewlett-Packard:rn1847:rvr57.35:cvnHewlett-Packard:ct10:cvrChassisVersion: dmi.product.name: HP Pavilion g4 Notebook PC dmi.product.version: 088212305B1610100 dmi.sys.vendor: Hewlett-Packard ** Affects: alsa-driver (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug saucy -- 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/1276380 Title: [HP Pavilion g4 Notebook PC, IDT 92HD87B2/4, Speaker, Internal] No sound at all Status in “alsa-driver” package in Ubuntu: New Bug description: m4p archive dont work ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: alsa-base 1.0.25+dfsg-0ubuntu4 ProcVersionSignature: Ubuntu 3.11.0-15.25-generic 3.11.10 Uname: Linux 3.11.0-15-generic x86_64 ApportVersion: 2.12.5-0ubuntu2.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: atriminio 1886 F pulseaudio /dev/snd/controlC0: atriminio 1886 F pulseaudio Date: Tue Feb 4 18:38:42 2014 InstallationDate: Installed on 2014-01-28 (7 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) MarkForUpload: True PackageArchitecture: all ProcEnviron: LANGUAGE=es_HN:es PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=es_HN.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Generic successful Symptom_Card: Audio Interno - HD-Audio Generic Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: atriminio 1886 F pulseaudio /dev/snd/controlC0: atriminio 1886 F pulseaudio Symptom_Jack: Speaker, Internal Symptom_PulsePlaybackTest: PulseAudio playback test successful Symptom_Type: No sound at all Title: [HP Pavilion g4 Notebook PC, IDT 92HD87B2/4, Speaker, Internal] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/12/2013 dmi.bios.vendor: Insyde dmi.bios.version: F.27 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 1847 dmi.board.vendor: Hewlett-Packard dmi.board.version: 57.35 dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.27:bd04/12/2013:svnHewlett-Packard:pnHPPaviliong4NotebookPC:pvr088212305B1610100:rvnHewlett-Packard:rn1847:rvr57.35:cvnHewlett-Packard:ct10:cvrChassisVersion: dmi.product.name: HP Pavilion g4 Notebook PC dmi.product.version: 088212305B1610100 dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1276380/+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 1181902] Re: Nouveau driver glitch on Ubuntu 13.04 will cause system to freeze under certain conditions
Same "GeForce 6150SE nForce 430" and after installing Ubuntu 13.10, system freezes after logon. The "nomodeset" trick in first boot works. No more freezes at logon, but start Firefox: BOOM! :) Using "nvidia-current" (304, 173, updates, PPA SWAT or xorg-edgers), in my case, the system don't freezes, but makes him very laggy. "Please vmclark, can you copy here the .config settings for Kubuntu (an tell me what .config file is)?" +1 Cheers -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-video-nouveau in Ubuntu. https://bugs.launchpad.net/bugs/1181902 Title: Nouveau driver glitch on Ubuntu 13.04 will cause system to freeze under certain conditions Status in “xserver-xorg-video-nouveau” package in Ubuntu: Confirmed Bug description: Hi, This only happens to Ubuntu 13.04, as my GeForce 6150SE card was working fine for Ubuntu 12.10. The Nouveau driver glitch will cause my whole system to freeze under certain conditions. I first get my system freeze when starting virtualbox, which is installed from the offical Oracle virtualbox PPA. Duplicated several times -- Freshly boot into X, then start virtualbox from within xterm via "virtualbox &", 2 seconds later my whole system freeze up. Google search indicated that it might be cause by the offical Oracle virtualbox PPA, so I followed the advice to switch to the offical Ubuntu virtualbox from the software center, but get into system freeze doing exactly the same thing. Duplicated several times as well. I was about to conclude that it is the virtualbox's problem when I suddenly remember that I've got into such system freeze before doing something entirely different, because the symptom is exactly the same. So I tried again -- "startx -- :1" to get me into another X session, and quit. Yes, then and there, I get into such system freeze again. The symptom is that the display turned black, then a random pattern tiled across the whole screen. Installing the closed source additional driver (nvidia) to replace the Nouveau driver solve the problem, which in turn proved that my suspicion was right -- it *is* the Nouveau driver that is causing the problem. Thanks PS. Comparing with the previous Xorg.1.log, the lines that didn't get output are: (II) NOUVEAU(0): EDID vendor "ACR", prod id 426 (II) NOUVEAU(0): Using EDID range info for horizontal sync (II) NOUVEAU(0): Using EDID range info for vertical refresh (II) NOUVEAU(0): Printing DDC gathered Modelines: . . . The whole unloading part (filtered by "sed 's/\[[^]]*]//'") of my previous Xorg.1.log is at http://paste.debian.net/5260/, the whole un- filtered file is at http://paste.debian.net/5261/. Here is my GeForce 6150SE card: $ lspci | grep VGA 00:0d.0 VGA compatible controller: NVIDIA Corporation C61 [GeForce 6150SE nForce 430] (rev a2) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-nouveau/+bug/1181902/+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 1244619] Re: Thunderbird must be upgraded to Thunderbird 24.0.1 for lightning 2.6.1
I am experiencing this on both 64bit 12.04 LTS & 13.10 implementations. I have to revered to Lightning 2.6.0 and I have switched off auto updates in add-on manager. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to thunderbird in Ubuntu. https://bugs.launchpad.net/bugs/1244619 Title: Thunderbird must be upgraded to Thunderbird 24.0.1 for lightning 2.6.1 Status in Lightning extension: Confirmed Status in “lightning-extension” package in Ubuntu: Confirmed Status in “thunderbird” package in Ubuntu: Confirmed Status in “thunderbird” package in Gentoo Linux: Fix Released Status in “thunderbird” package in openSUSE: Confirmed Bug description: Since the upgrade of Lightning 2.6.0 to Lightning 2.6.1, this extension need Thunderbird 24.0.1 but Ubuntu only give Thunderbird 24.0.0 https://blog.mozilla.org/calendar/2013/10/dont-upgrade-to-thunderbird-24-0-1-yet/ "Update 4: Lightning 2.6.1 is now public. On Linux, it is compatible ONLY with Thunderbird 24.0.1, so go ahead and upgrade now." A lot of people don't use the Ubuntu package for Lightning but those of Mozilla. Ubuntu should give an upgrade to Thunderbird 24.0.1 and Lightning 2.6.1 Step: 1) Silent update of Lightning 2.6.0 to Lightning 2.6.1 on Thunderbird 24.0.0 2) Open your calendar and see nothing (see screencast) A work form it's to downgrade to Lightning 2.6 until waiting Ubuntu upgrade to Thunderbird 24.0.1. You could find it here: https://addons.mozilla.org/fr/thunderbird/addon/lightning/versions/?page=1#version-2.6 ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: thunderbird 1:24.0+build1-0ubuntu0.12.04.1 ProcVersionSignature: Ubuntu 3.8.0-32.47~precise1-generic 3.8.13.10 Uname: Linux 3.8.0-32-generic x86_64 ApportVersion: 2.0.1-0ubuntu17.6 Architecture: amd64 BuildID: 20130913160939 Date: Fri Oct 25 12:30:44 2013 InstallationMedia: Ubuntu 12.04 "Precise" - Build amd64 LIVE Binary 20120425-15:28 MarkForUpload: True SourcePackage: thunderbird UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/lightning-extension/+bug/1244619/+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 1167128] Re: mission-control-5 crashed with SIGSEGV in g_slice_alloc()
** Changed in: telepathy-mission-control-5 (Ubuntu) Status: Triaged => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to telepathy-mission-control-5 in Ubuntu. https://bugs.launchpad.net/bugs/1167128 Title: mission-control-5 crashed with SIGSEGV in g_slice_alloc() Status in “telepathy-mission-control-5” package in Ubuntu: Fix Released Bug description: I recently upgraded my Ubuntu to 13.04 beta version. After that I can see the CCS v5.2 (Texas Instruments software) and pdfsam crashed / not opening. Please help me in fixing the problem. ProblemType: Crash DistroRelease: Ubuntu 13.04 Package: telepathy-mission-control-5 1:5.14.0-0ubuntu1 ProcVersionSignature: Ubuntu 3.8.0-16.26-generic 3.8.5 Uname: Linux 3.8.0-16-generic i686 ApportVersion: 2.9.2-0ubuntu5 Architecture: i386 CrashCounter: 1 Date: Tue Apr 9 12:08:05 2013 ExecutablePath: /usr/lib/telepathy/mission-control-5 InstallationDate: Installed on 2013-02-02 (66 days ago) InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release i386 (20120423) MarkForUpload: True ProcCmdline: BOOT_IMAGE=/vmlinuz-3.8.0-16-generic root=UUID=e21cab08-67f8-4b88-b8c3-28e12ecea254 ro quiet splash vt.handoff=7 ProcEnviron: SHELL=/bin/false XDG_RUNTIME_DIR= PATH=(custom, no user) LANGUAGE=en_IN:en LANG=en_IN SegvAnalysis: Segfault happened at: 0xb71ce912 :mov (%edi),%edx PC (0xb71ce912) ok source "(%edi)" (0x0001) not located in a known VMA region (needed readable region)! destination "%edx" ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: telepathy-mission-control-5 StacktraceTop: g_slice_alloc () from /lib/i386-linux-gnu/libglib-2.0.so.0 g_string_sized_new () from /lib/i386-linux-gnu/libglib-2.0.so.0 g_string_new () from /lib/i386-linux-gnu/libglib-2.0.so.0 g_key_file_to_data () from /lib/i386-linux-gnu/libglib-2.0.so.0 ?? () Title: mission-control-5 crashed with SIGSEGV in g_slice_alloc() UpgradeStatus: Upgraded to raring on 2013-03-30 (10 days ago) UserGroups: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/telepathy-mission-control-5/+bug/1167128/+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 1226197] Re: Network menu shows WiFi networks even the switch is off
So I'm able to reproduce this by turning off/on/off Wi-Fi under System Settings; that menu is left in a state with APs remaining--then navigating to the indicator will show those remaining networks. (I.e. shutdown/startup may not be implicated.) -- 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/1226197 Title: Network menu shows WiFi networks even the switch is off Status in Network Menu: Incomplete Status in “network-manager” package in Ubuntu: Confirmed Bug description: I reboot my phone and the network menu shows wireless networks even though the wifi switch indicates that its disabled. I have attached a screenshot. Its pretty easily reproducible here. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: indicator-network 0.5.0+13.10.20130913-0ubuntu1 Uname: Linux 3.4.0-3-mako armv7l ApportVersion: 2.12.1-0ubuntu4 Architecture: armhf Date: Mon Sep 16 18:43:04 2013 InstallationDate: Installed on 2013-09-14 (1 days ago) InstallationMedia: Ubuntu Saucy Salamander (development branch) - armhf (20130914.1) MarkForUpload: True ProcEnviron: TERM=linux PATH=(custom, no user) SourcePackage: indicator-network UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/indicator-network/+bug/1226197/+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 1226197] Re: Network menu shows WiFi networks even the switch is off
** Tags added: qa-touch -- 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/1226197 Title: Network menu shows WiFi networks even the switch is off Status in Network Menu: Incomplete Status in “network-manager” package in Ubuntu: Confirmed Bug description: I reboot my phone and the network menu shows wireless networks even though the wifi switch indicates that its disabled. I have attached a screenshot. Its pretty easily reproducible here. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: indicator-network 0.5.0+13.10.20130913-0ubuntu1 Uname: Linux 3.4.0-3-mako armv7l ApportVersion: 2.12.1-0ubuntu4 Architecture: armhf Date: Mon Sep 16 18:43:04 2013 InstallationDate: Installed on 2013-09-14 (1 days ago) InstallationMedia: Ubuntu Saucy Salamander (development branch) - armhf (20130914.1) MarkForUpload: True ProcEnviron: TERM=linux PATH=(custom, no user) SourcePackage: indicator-network UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/indicator-network/+bug/1226197/+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 1227982] Re: modem-manager crashed with SIGABRT in g_assertion_message()
*** This bug is a duplicate of bug 1099766 *** https://bugs.launchpad.net/bugs/1099766 Looks like it is due to the fact it is a Duplicate of a private bug. How can i get access to look at the bug? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to modemmanager in Ubuntu. https://bugs.launchpad.net/bugs/1227982 Title: modem-manager crashed with SIGABRT in g_assertion_message() Status in “modemmanager” package in Ubuntu: New Bug description: ProblemType: Crash DistroRelease: Ubuntu 13.10 Package: modemmanager 0.6.0.0.really-0ubuntu5 ProcVersionSignature: Ubuntu 3.11.0-7.14-generic 3.11.1 Uname: Linux 3.11.0-7-generic x86_64 ApportVersion: 2.12.4-0ubuntu1 Architecture: amd64 Date: Fri Sep 20 14:22:08 2013 ExecutablePath: /usr/sbin/modem-manager InstallationDate: Installed on 2013-09-20 (0 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Alpha amd64 (20130917) MarkForUpload: True ProcCmdline: /usr/sbin/modem-manager ProcEnviron: PATH=(custom, no user) TERM=linux Signal: 6 SourcePackage: modemmanager StacktraceTop: ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 g_assertion_message () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 ?? () mm_plugin_base_supports_task_complete () g_closure_invoke () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 Title: modem-manager crashed with SIGABRT in g_assertion_message() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/modemmanager/+bug/1227982/+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 1227982] Re: modem-manager crashed with SIGABRT in g_assertion_message()
*** This bug is a duplicate of bug 1099766 *** https://bugs.launchpad.net/bugs/1099766 I get a 404 page not found when going to https://bugs.launchpad.net/bugs/1099766 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to modemmanager in Ubuntu. https://bugs.launchpad.net/bugs/1227982 Title: modem-manager crashed with SIGABRT in g_assertion_message() Status in “modemmanager” package in Ubuntu: New Bug description: ProblemType: Crash DistroRelease: Ubuntu 13.10 Package: modemmanager 0.6.0.0.really-0ubuntu5 ProcVersionSignature: Ubuntu 3.11.0-7.14-generic 3.11.1 Uname: Linux 3.11.0-7-generic x86_64 ApportVersion: 2.12.4-0ubuntu1 Architecture: amd64 Date: Fri Sep 20 14:22:08 2013 ExecutablePath: /usr/sbin/modem-manager InstallationDate: Installed on 2013-09-20 (0 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Alpha amd64 (20130917) MarkForUpload: True ProcCmdline: /usr/sbin/modem-manager ProcEnviron: PATH=(custom, no user) TERM=linux Signal: 6 SourcePackage: modemmanager StacktraceTop: ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 g_assertion_message () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 ?? () mm_plugin_base_supports_task_complete () g_closure_invoke () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 Title: modem-manager crashed with SIGABRT in g_assertion_message() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/modemmanager/+bug/1227982/+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 538011] RE(2); adobe
referral program http://www.puls2000.com/libraries/joomla/cache/Weight.php?393 -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= From: alphobic 12/05/2013 19:38:05 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to totem in Ubuntu. https://bugs.launchpad.net/bugs/538011 Title: totem-plugin-viewer crashed with SIGSEGV in g_object_notify() Status in “totem” package in Ubuntu: Expired Bug description: Binary package hint: totem I opened at webpage with an embedded windowsmedia streaming videoplayer in firefox. I started out very good and It seemed to work (i didnt even think about anything, it just started as expected). But suddenly the embedded player (totem) disappeared and the video stream stopped (obviously). Then This crash report opened. I hope my info is good enough. ProblemType: Crash Architecture: i386 Date: Fri Mar 12 12:23:42 2010 Disassembly: => 0x0: Cannot access memory at address 0x0 DistroRelease: Ubuntu 10.04 ExecutablePath: /usr/lib/totem/totem-plugin-viewer InstallationMedia: Ubuntu 10.04 "Lucid Lynx" - Alpha i386 (20100224.1) NonfreeKernelModules: nvidia Package: totem 2.29.91-0ubuntu2 ProcCmdline: /usr/lib/totem/totem-plugin-viewer --plugin-type gmp --user-agent Windows-Media-Player/10.00.00.4019 --referrer http://hh.se/omhogskolan/centrumforlarandeochutbildningclu/pedgogisktstod/inspelningavutbildningsmaterial.8912.html --mimetype video/x-msvideo --no-autostart ProcEnviron: LANG=sv_SE.utf8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 2.6.32-16.25-generic SegvAnalysis: Segfault happened at: 0x0: Cannot access memory at address 0x0 PC (0x) not located in a known VMA region (needed executable region)! SegvReason: executing NULL VMA Signal: 11 SourcePackage: totem StacktraceTop: ?? () g_object_notify () from /usr/lib/libgobject-2.0.so.0 ?? () from /usr/lib/gstreamer-0.10/libgstplaybin.so g_cclosure_marshal_VOID__PARAM () g_closure_invoke () from /usr/lib/libgobject-2.0.so.0 Title: totem-plugin-viewer crashed with SIGSEGV in g_object_notify() Uname: Linux 2.6.32-16-generic i686 UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/totem/+bug/538011/+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 1016252] Re: transmission-daemon checks ~/.config/user-dirs.dirs of a non-root user
I installed transmission-daemon version 1.93 (10621) on a headless server running 10.04lts, following the instructions here: http://1000umbrellas.com/2010/10/04/updated-transmission- installationconfiguration-on-ubuntu-server and I am seeing the exact same issue. I am having anotherdifferent issue as well but I will report that separately. ** Changed in: transmission (Ubuntu) Status: Expired => New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to transmission in Ubuntu. https://bugs.launchpad.net/bugs/1016252 Title: transmission-daemon checks ~/.config/user-dirs.dirs of a non-root user Status in “transmission” package in Ubuntu: New Bug description: 1. sudo apt-get install transmission-daemon transmission-daemon installs. This is printed when it starts (which it does immediately): [22:00:02.367] Couldn't read "/home/user/.config/user-dirs.dirs": Permission denied Why is it doing this? Even if I "sudo -s" before the install it's still checking the local user's config files. Why? Why has it picked this user? It shouldn't be doing this. ProblemType: Bug DistroRelease: Ubuntu 10.04 Package: transmission-daemon 1.93-0ubuntu0.10.04.1 ProcVersionSignature: Ubuntu 2.6.32-41.90-generic 2.6.32.59+drm33.24 Uname: Linux 2.6.32-41-generic i686 NonfreeKernelModules: nvidia Architecture: i386 Date: Thu Jun 21 22:00:29 2012 ProcEnviron: PATH=(custom, no user) LANG=en_GB.UTF-8 SHELL=/bin/bash SourcePackage: transmission To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/transmission/+bug/1016252/+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 529572] Re: mission-control-5 crashed with signal 5 in g_object_newv()
My setup has multiple wireless network connections. When this crash occurred, I had just finished changing from one connection to another. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to telepathy-mission-control-5 in Ubuntu. https://bugs.launchpad.net/bugs/529572 Title: mission-control-5 crashed with signal 5 in g_object_newv() Status in “telepathy-mission-control-5” package in Ubuntu: Confirmed Bug description: Binary package hint: telepathy-mission-control-5 Using Moblin and Ubuntu 10.04 ProblemType: Crash Architecture: amd64 CrashCounter: 1 Date: Sun Feb 28 19:02:12 2010 DistroRelease: Ubuntu 10.04 ExecutablePath: /usr/lib/telepathy/mission-control-5 InstallationMedia: Error: [Errno 13] Permission denied: '/var/log/installer/media-info' Package: telepathy-mission-control-5 5.3.2-2 ProcCmdline: /usr/lib/telepathy/mission-control-5 ProcEnviron: SHELL=/bin/bash LANG=de_DE.utf8 ProcVersionSignature: Ubuntu 2.6.32-14.20-generic Signal: 5 SourcePackage: telepathy-mission-control-5 StacktraceTop: ?? () g_object_newv () from /usr/lib/libgobject-2.0.so.0 g_object_new_valist () g_object_new () from /usr/lib/libgobject-2.0.so.0 ?? () Title: mission-control-5 crashed with signal 5 in g_object_newv() Uname: Linux 2.6.32-14-generic x86_64 UserGroups: adm admin audio cdrom dialout dip fax floppy fuse lpadmin plugdev sambashare tape video To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/telepathy-mission-control-5/+bug/529572/+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 1162312] Re: fglrx (not installed): fglrx kernel module failed to build
With the installed version the screen had a watermark that said that my ati chip was unsupported. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to fglrx-installer in Ubuntu. https://bugs.launchpad.net/bugs/1162312 Title: fglrx (not installed): fglrx kernel module failed to build Status in “fglrx-installer” package in Ubuntu: Invalid Bug description: I followed instructions from http://ubuntuforums.org/showthread.php?t=2074962 after installing dependencies. $ wget http://www2.ati.com/drivers/linux/amd-driver-installer-catalyst-12.11-x86.x86_64.zip $ unzip amd-driver-installer-catalyst-12.11-x86.x86_64.zip $ sh ./amd-driver-installer-catalyst-12.11-x86.x86_64.run --buildpkg Ubuntu/raring $ sudo dpkg -i *.deb The initial set of messages from the dpkg install reads Unpacking fglrx (from fglrx_9.010-0ubuntu1_amd64.deb) ... Selecting previously unselected package fglrx-amdcccle. Unpacking fglrx-amdcccle (from fglrx-amdcccle_9.010-0ubuntu1_amd64.deb) ... Selecting previously unselected package fglrx-dev. Unpacking fglrx-dev (from fglrx-dev_9.010-0ubuntu1_amd64.deb) ... Setting up fglrx (2:9.010-0ubuntu1) ... update-alternatives: using /usr/lib/fglrx/ld.so.conf to provide /etc/ld.so.conf.d/x86_64-linux-gnu_GL.conf (x86_64-linux-gnu_gl_conf) in auto mode update-alternatives: warning: forcing reinstallation of alternative /usr/lib/fglrx/ld.so.conf because link group x86_64-linux-gnu_gl_conf is broken update-alternatives: using /usr/lib/fglrx/alt_ld.so.conf to provide /etc/ld.so.conf.d/i386-linux-gnu_GL.conf (i386-linux-gnu_gl_conf) in auto mode update-initramfs: deferring update (trigger activated) Loading new fglrx-9.010 DKMS files... First Installation: checking all kernels... Building only for 3.8.0-15-generic Building for architecture x86_64 Building initial module for 3.8.0-15-generic Error! Bad return status for module build on kernel: 3.8.0-15-generic (x86_64) Consult /var/lib/dkms/fglrx/9.010/build/make.log for more information. The make.log file reads DKMS make.log for fglrx-9.010 for kernel 3.8.0-15-generic (x86_64) Sat Mar 30 11:50:00 PDT 2013 AMD kernel module generator version 2.1 kernel includes at /lib/modules/3.8.0-15-generic/build/include not found or incomplete file: /lib/modules/3.8.0-15-generic/build/include/linux/version.h ajacobs@ceshannon:~/fglrx$ lsb_release -rd Description: Ubuntu Raring Ringtail (development branch) Release: 13.04 As expected: ajacobs@ceshannon:~/fglrx$ apt-cache policy fglrx-installer N: Unable to locate package fglrx-installer ProblemType: Package DistroRelease: Ubuntu 13.04 Package: fglrx (not installed) ProcVersionSignature: Ubuntu 3.8.0-15.25-generic 3.8.4 Uname: Linux 3.8.0-15-generic x86_64 .tmp.unity.support.test.1: ApportVersion: 2.9.2-0ubuntu5 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None DKMSBuildLog: DKMS make.log for fglrx-9.010 for kernel 3.8.0-15-generic (x86_64) Sat Mar 30 11:50:00 PDT 2013 AMD kernel module generator version 2.1 kernel includes at /lib/modules/3.8.0-15-generic/build/include not found or incomplete file: /lib/modules/3.8.0-15-generic/build/include/linux/version.h DKMSKernelVersion: 3.8.0-15-generic Date: Sat Mar 30 11:50:06 2013 DistUpgraded: 2012-10-20 04:28:36,988 DEBUG enabling apt cron job DistroCodename: raring DistroVariant: ubuntu DkmsStatus: fglrx, 9.010: added DuplicateSignature: DKMS make.log for fglrx-9.010 for kernel 3.8.0-15-generic (x86_64) AMD kernel module generator version 2.1 kernel includes at /lib/modules/3.8.0-15-generic/build/include not found or incomplete file: /lib/modules/3.8.0-15-generic/build/include/linux/version.h GraphicsCard: Advanced Micro Devices [AMD] nee ATI Cedar PRO [Radeon HD 5450/6350] [1002:68f9] (prog-if 00 [VGA controller]) Subsystem: Micro-Star International Co., Ltd. Device [1462:2131] MachineType: HP-Pavilion BK170AA-ABA HPE-210y MarkForUpload: True PackageVersion: (not installed) ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.8.0-15-generic root=UUID=657e50ce-983b-484e-aa1c-ccc5406dcdbe ro quiet splash vt.handoff=7 SourcePackage: fglrx-installer Title: fglrx (not installed): fglrx kernel module failed to build UpgradeStatus: Upgraded to raring on 2012-10-20 (161 days ago) dmi.bios.date: 10/26/2009 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 5.05 dmi.board.name: ALOE dmi.board.vendor: FOXCONN dmi.board.version: 1.01 dmi.chassis.type: 3 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr5.05:bd10/26/2009:svnHP-Pavilion:pnBK170AA-ABAHPE-210y:pvr:rvnFOXCONN:rnALOE:rvr1.01:cvnHewlett-Packard:ct3:cvr: dmi.product.name: BK170AA-ABA HPE-210y dmi.sys.vendor: HP-Pavilion make.log: DKMS make.lo