[Bug 1960596] [NEW] no sound after upgrade to 21.10

2022-02-11 Thread Vadim Peretokin
Public bug reported:

I had sound working in 21.04, did the mandatory upgrade to 21.10 and all
sound is gone - in videos, browsers, games. What could be the problem?

ProblemType: Bug
DistroRelease: Ubuntu 21.10
Package: pipewire 0.3.32-1
ProcVersionSignature: Ubuntu 5.13.0-28.31-generic 5.13.19
Uname: Linux 5.13.0-28-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.11-0ubuntu71
Architecture: amd64
CasperMD5CheckResult: unknown
CurrentDesktop: ubuntu:GNOME
Date: Fri Feb 11 08:59:34 2022
InstallationDate: Installed on 2020-12-21 (416 days ago)
InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
SourcePackage: pipewire
UpgradeStatus: Upgraded to impish on 2022-02-10 (0 days ago)

** Affects: pipewire (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug impish

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1960596

Title:
  no sound after upgrade to 21.10

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pipewire/+bug/1960596/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 970260] Re: Setting up memtest86+ hangs because of "grub-probe: error: unknown filesystem"

2022-02-10 Thread Vadim Peretokin
It's still a problem when upgrading from 21.04 to 21.10, grub-mount hung
trying to query an unresponsive drive.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/970260

Title:
  Setting up memtest86+ hangs because of  "grub-probe: error: unknown
  filesystem"

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/970260/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1959465] Re: Mudlet not respecting user-selected server data encoding setting

2022-01-31 Thread Vadim Peretokin
Hi!

> When connecting to MUME with Force CHARSET negotiation enabled (box
NOT checked under Special settings)

There is no 'force charset negotiation on' option, just an option to
turn it off which is why I think you're confused.

The way it works is: you can either allow the server to set the
encoding, or you want to choose it yourself in which case you don't
allow it.

It's unfortunate that MUME is giving preference to ISO 8859-1 - it
should give preference to UTF-8.

I hope that helps!

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1959465

Title:
  Mudlet not respecting user-selected server data encoding setting

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mudlet/+bug/1959465/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1924895] Re: Settings crashes as soon as it is opened

2021-04-19 Thread Vadim Peretokin
Indeed I had the first two issues. Settings don't seem to crash after a
reboot - will update this when it happens again.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1924895

Title:
  Settings crashes as soon as it is opened

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1924895/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1924895] [NEW] Settings crashes as soon as it is opened

2021-04-18 Thread Vadim Peretokin
Public bug reported:

Just opening the settings causes it to almost immediately crash.


❯ gnome-control-center


(gnome-control-center:12969): dconf-WARNING **: 09:14:26.286: failed to commit 
changes to dconf: Could not connect: Connection refused
Error creating rfkill proxy: (null)
Segmentation fault (core dumped)
~ 
❯ 
~ 
❯ gnome-control-center user-accounts

(gnome-control-center:13142): dconf-WARNING **: 09:15:10.855: failed to
commit changes to dconf: Could not connect: Connection refused

(gnome-control-center:13142): dconf-WARNING **: 09:15:11.085: failed to commit 
changes to dconf: Could not connect: Connection refused
Segmentation fault (core dumped)
~ took 16s 
❯ gdb gnome-control-center
GNU gdb (Ubuntu 9.2-0ubuntu1~20.04) 9.2
Copyright (C) 2020 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later 
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.
Type "show copying" and "show warranty" for details.
This GDB was configured as "x86_64-linux-gnu".
Type "show configuration" for configuration details.
For bug reporting instructions, please see:
.
Find the GDB manual and other documentation resources online at:
.

For help, type "help".
Type "apropos word" to search for commands related to "word"...
Reading symbols from gnome-control-center...
(No debugging symbols found in gnome-control-center)
(gdb) r
Starting program: /usr/bin/gnome-control-center 
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[New Thread 0x7fffea9e0700 (LWP 13237)]
[New Thread 0x7fffdf05b700 (LWP 13238)]
[New Thread 0x7fffde85a700 (LWP 13239)]
[New Thread 0x7fffde059700 (LWP 13240)]
[New Thread 0x7fffdd858700 (LWP 13241)]
[New Thread 0x7fffdcc17700 (LWP 13242)]
[New Thread 0x7fffc7fff700 (LWP 13243)]
[New Thread 0x7fffc77fe700 (LWP 13244)]
[New Thread 0x7fffc6ffd700 (LWP 13245)]

(gnome-control-center:13233): dconf-WARNING **: 09:15:38.054: failed to commit 
changes to dconf: Could not connect: Connection refused
Error creating rfkill proxy: (null)

Thread 8 "pool-gnome-cont" received signal SIGSEGV, Segmentation fault.
[Switching to Thread 0x7fffc7fff700 (LWP 13243)]
0x77ca6ac3 in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
(gdb) bt
#0  0x77ca6ac3 in  () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
#1  0x77ca6e1c in  () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x7637e5a1 in __nptl_deallocate_tsd () at pthread_create.c:301
#3  0x7637f62a in __nptl_deallocate_tsd () at pthread_create.c:256
#4  start_thread (arg=) at pthread_create.c:488
#5  0x762a6293 in clone () at 
../sysdeps/unix/sysv/linux/x86_64/clone.S:95
(gdb) q
A debugging session is active.

Inferior 1 [process 13233] will be killed.

Quit anyway? (y or n) y
~ took 20s 
❯ gnome-control-center --version
gnome-control-center 3.36.5
~ 
❯ ubuntu-bug gnome-control-center

(gio open:15213): GLib-GIO-CRITICAL **: 09:17:11.048:
g_dbus_connection_flush: assertion 'G_IS_DBUS_CONNECTION (connection)'
failed

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: gnome-control-center 1:3.36.5-0ubuntu1
ProcVersionSignature: Ubuntu 5.4.0-71.79-generic 5.4.101
Uname: Linux 5.4.0-71-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.16
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Sun Apr 18 09:16:22 2021
EcryptfsInUse: Yes
InstallationDate: Installed on 2017-02-15 (1522 days ago)
InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719)
SourcePackage: gnome-control-center
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: gnome-control-center (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug focal

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1924895

Title:
  Settings crashes as soon as it is opened

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1924895/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1880405] Re: Unresponsive GUI and journal flooded with: JS ERROR: TypeError: null has no properties _onFocusChanged@resource:///org/gnome/shell/ui/closeDialog.js:135:9

2021-03-11 Thread Vadim Peretokin
Is the fix available in 20.04 LTS, or just 20.10 only?

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1880405

Title:
  Unresponsive GUI and journal flooded with: JS ERROR: TypeError: null
  has no properties
  _onFocusChanged@resource:///org/gnome/shell/ui/closeDialog.js:135:9

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-shell/+bug/1880405/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1912597] [NEW] Workrave does not detect mouse/keyboard free

2021-01-21 Thread Vadim Peretokin
Public bug reported:

When workrave prompts me for a break and I take one, it does not detect
this - so it keeps complaining the computer is still in use and then
gives the nasty error.

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: workrave 1.10.37-1
ProcVersionSignature: Ubuntu 5.8.0-36.40~20.04.1-generic 5.8.18
Uname: Linux 5.8.0-36-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.11-0ubuntu27.14
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Thu Jan 21 09:15:19 2021
InstallationDate: Installed on 2020-12-21 (30 days ago)
InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
SourcePackage: workrave
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: workrave (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug focal

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1912597

Title:
  Workrave does not detect mouse/keyboard free

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/workrave/+bug/1912597/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1909543] [NEW] "Failed to start Sound Service" in security logs

2020-12-29 Thread Vadim Peretokin
Public bug reported:

Security logs are complaining about failing to start the sound service,
on a new installation of Ubuntu 20.04 LTS. This is concerning.

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: pulseaudio 1:13.99.1-1ubuntu3.8
ProcVersionSignature: Ubuntu 5.4.0-58.64-generic 5.4.73
Uname: Linux 5.4.0-58-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.14
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  vadi   3182 F pulseaudio
 /dev/snd/pcmC0D0c:   vadi   3182 F...m pulseaudio
 /dev/snd/pcmC0D0p:   vadi   3182 F...m pulseaudio
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Tue Dec 29 09:35:00 2020
EcryptfsInUse: Yes
InstallationDate: Installed on 2017-02-15 (1412 days ago)
InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719)
SourcePackage: pulseaudio
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 07/30/2020
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 1.25.3
dmi.board.name: 0T6HHJ
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 9
dmi.chassis.vendor: Dell Inc.
dmi.modalias: 
dmi:bvnDellInc.:bvr1.25.3:bd07/30/2020:svnDellInc.:pnLatitudeE7470:pvr:rvnDellInc.:rn0T6HHJ:rvrA00:cvnDellInc.:ct9:cvr:
dmi.product.family: Latitude
dmi.product.name: Latitude E7470
dmi.product.sku: 06DC
dmi.sys.vendor: Dell Inc.

** Affects: pulseaudio (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug focal

** Attachment added: "Selection_560.png"
   
https://bugs.launchpad.net/bugs/1909543/+attachment/5447585/+files/Selection_560.png

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1909543

Title:
  "Failed to start Sound Service" in security logs

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1909543/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1908889] [NEW] "Failed to install file: not supported" error

2020-12-21 Thread Vadim Peretokin
Public bug reported:

On a brand new installation of Ubuntu 20.04 LTS, trying to install a
.deb (say, from discord.com) gives a "Failed to install file: not
supported" error.

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: ubuntu-software (not installed)
ProcVersionSignature: Ubuntu 5.4.0-58.64-generic 5.4.73
Uname: Linux 5.4.0-58-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.14
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Mon Dec 21 10:59:49 2020
InstallationDate: Installed on 2020-12-21 (0 days ago)
InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
SourcePackage: gnome-software
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: gnome-software (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug focal

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1908889

Title:
  "Failed to install file: not supported" error

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1908889/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1902446] Re: Not possible to see list of wifi networks

2020-11-03 Thread Vadim Peretokin
The usual gnome environment.

Not much in journalctl:

nov 03 22:59:57 volga audit[9670]: AVC apparmor="DENIED" operation="open" 
profile="snap.hiri.hiri" name="/home/vadi/.netrc" pid=9670 comm="hirimain" 
requested_mask="r" denied_mask="r" fsuid=1000 ouid=1000
nov 03 22:59:57 volga kernel: audit: type=1400 audit(1604440797.544:5054): 
apparmor="DENIED" operation="open" profile="snap.hiri.hiri" 
name="/home/vadi/.netrc" pid=9670 comm="hirimain" requested_mask="r" denied_m>
nov 03 23:00:10 volga kernel: [UFW BLOCK] IN=wlp1s0 OUT= 
MAC=01:00:5e:00:00:01:08:26:97:d0:93:a0:08:00 SRC=192.168.1.1 DST=224.0.0.1 
LEN=32 TOS=0x00 PREC=0xC0 TTL=1 ID=55594 PROTO=2 
nov 03 23:00:42 volga kernel: [UFW BLOCK] IN=wlp1s0 OUT= 
MAC=01:00:5e:00:00:01:08:26:97:d0:93:a2:08:00 SRC=0.0.0.0 DST=224.0.0.1 LEN=36 
TOS=0x00 PREC=0x00 TTL=1 ID=1 PROTO=2 
nov 03 23:00:43 volga kernel: [UFW BLOCK] IN=wlp1s0 OUT= 
MAC=01:00:5e:00:00:fb:92:d1:cf:19:a3:4c:08:00 SRC=192.168.1.226 DST=224.0.0.251 
LEN=32 TOS=0x00 PREC=0xC0 TTL=1 ID=0 DF PROTO=2 
nov 03 23:00:50 volga audit[9649]: AVC apparmor="DENIED" operation="open" 
profile="snap.hiri.hiri" name="/home/vadi/.netrc" pid=9649 comm="BG" 
requested_mask="r" denied_mask="r" fsuid=1000 ouid=1000
nov 03 23:00:50 volga kernel: audit: type=1400 audit(1604440850.353:5055): 
apparmor="DENIED" operation="open" profile="snap.hiri.hiri" 
name="/home/vadi/.netrc" pid=9649 comm="BG" requested_mask="r" denied_mask="r>
nov 03 23:00:50 volga audit[9649]: AVC apparmor="DENIED" operation="open" 
profile="snap.hiri.hiri" name="/home/vadi/.netrc" pid=9649 comm="BG" 
requested_mask="r" denied_mask="r" fsuid=1000 ouid=1000
nov 03 23:00:50 volga kernel: audit: type=1400 audit(1604440850.577:5056): 
apparmor="DENIED" operation="open" profile="snap.hiri.hiri" 
name="/home/vadi/.netrc" pid=9649 comm="BG" requested_mask="r" denied_mask="r>
nov 03 23:00:50 volga audit[9649]: AVC apparmor="DENIED" operation="open" 
profile="snap.hiri.hiri" name="/home/vadi/.netrc" pid=9649 comm="BG" 
requested_mask="r" denied_mask="r" fsuid=1000 ouid=1000
nov 03 23:00:50 volga kernel: audit: type=1400 audit(1604440850.701:5057): 
apparmor="DENIED" operation="open" profile="snap.hiri.hiri" 
name="/home/vadi/.netrc" pid=9649 comm="BG" requested_mask="r" denied_mask="r>
nov 03 23:00:51 volga audit[9649]: AVC apparmor="DENIED" operation="open" 
profile="snap.hiri.hiri" name="/home/vadi/.netrc" pid=9649 comm="Worker" 
requested_mask="r" denied_mask="r" fsuid=1000 ouid=1000
nov 03 23:00:51 volga kernel: audit: type=1400 audit(1604440851.661:5058): 
apparmor="DENIED" operation="open" profile="snap.hiri.hiri" 
name="/home/vadi/.netrc" pid=9649 comm="Worker" requested_mask="r" denied_mas>
nov 03 23:01:11 volga kernel: [UFW BLOCK] IN=wlp1s0 OUT= 
MAC=01:00:5e:00:00:01:08:26:97:d0:93:a0:08:00 SRC=192.168.1.1 DST=224.0.0.1 
LEN=32 TOS=0x00 PREC=0xC0 TTL=1 ID=61275 PROTO=2 
nov 03 23:01:18 volga gnome-shell[3615]: 
../clutter/clutter/clutter-actor.c:10558: The clutter_actor_set_allocation() 
function can only be called from within the implementation of the 
ClutterActor::allocate() vir>
nov 03 23:01:21 volga systemd[2315]: Started Application launched by 
gsd-media-keys.
nov 03 23:01:21 volga systemd[2315]: Started VTE child process 69735 launched 
by x-terminal-emulator process 39586.
nov 03 23:01:21 volga systemd[2315]: 
gnome-launched-x-terminal-emulator-69726.scope: Succeeded.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1902446

Title:
  Not possible to see list of wifi networks

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1902446/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1902446] [NEW] Not possible to see list of wifi networks

2020-11-01 Thread Vadim Peretokin
Public bug reported:

Using the default 'light' theme, the network listing is impossible to
read

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: network-manager 1.22.10-1ubuntu2.1
ProcVersionSignature: Ubuntu 5.4.0-52.57-generic 5.4.65
Uname: Linux 5.4.0-52-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.10
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Sun Nov  1 19:41:38 2020
EcryptfsInUse: Yes
IfupdownConfig:
 # interfaces(5) file used by ifup(8) and ifdown(8)
 auto lo
 iface lo inet loopback
InstallationDate: Installed on 2017-02-15 (1355 days ago)
InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719)
SourcePackage: network-manager
UpgradeStatus: No upgrade log present (probably fresh install)
nmcli-nm:
 RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  WIFI  
   WWAN-HW  WWAN
 running  1.22.10  connected  started  full  enabled enabled  
enabled  enabled  enabled

** Affects: network-manager (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug focal

** Attachment added: "Workspace 1_350.png"
   
https://bugs.launchpad.net/bugs/1902446/+attachment/5430088/+files/Workspace%201_350.png

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1902446

Title:
  Not possible to see list of wifi networks

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1902446/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1900114] [NEW] Ubuntu locks up when low battery

2020-10-16 Thread Vadim Peretokin
Public bug reported:

Instead of giving a low battery warning, Ubuntu pretty consistently
locks up and freezes instead. Not even the mouse can move.

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: linux-image-5.4.0-51-generic 5.4.0-51.56
ProcVersionSignature: Ubuntu 5.4.0-51.56-generic 5.4.65
Uname: Linux 5.4.0-51-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.8
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  vadi   3918 F pulseaudio
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Fri Oct 16 11:42:34 2020
EcryptfsInUse: Yes
HibernationDevice: RESUME=UUID=8c0e25d4-6e36-428e-b354-4c71b99db752
InstallationDate: Installed on 2017-02-15 (1338 days ago)
InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719)
Lsusb:
 Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
 Bus 001 Device 003: ID 8087:0a2b Intel Corp. 
 Bus 001 Device 002: ID 0bda:5686 Realtek Semiconductor Corp. 
Integrated_Webcam_HD
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: Dell Inc. Latitude E7470
ProcFB: 0 i915drmfb
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-51-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
RelatedPackageVersions:
 linux-restricted-modules-5.4.0-51-generic N/A
 linux-backports-modules-5.4.0-51-generic  N/A
 linux-firmware1.187.3
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 07/30/2020
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 1.25.3
dmi.board.name: 0T6HHJ
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 9
dmi.chassis.vendor: Dell Inc.
dmi.modalias: 
dmi:bvnDellInc.:bvr1.25.3:bd07/30/2020:svnDellInc.:pnLatitudeE7470:pvr:rvnDellInc.:rn0T6HHJ:rvrA00:cvnDellInc.:ct9:cvr:
dmi.product.family: Latitude
dmi.product.name: Latitude E7470
dmi.product.sku: 06DC
dmi.sys.vendor: Dell Inc.

** Affects: linux (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug focal

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1900114

Title:
  Ubuntu locks up when low battery

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1900114/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1883421] Re: Ubuntu Software can't install .deb files

2020-06-16 Thread Vadim Peretokin
I imagine it is gnome-software.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1883421

Title:
  Ubuntu Software can't install .deb files

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1883421/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1883421] [NEW] Ubuntu Software can't install .deb files

2020-06-14 Thread Vadim Peretokin
Public bug reported:

Download the .deb from https://zoom.us/support/download and try to
"Open" it - you'll get an error message saying the tool for installing
software doesn't know what to do with a software installer file.

Attached is a screenshot.

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: ubuntu-software (not installed)
ProcVersionSignature: Ubuntu 5.4.0-38.42-generic 5.4.44
Uname: Linux 5.4.0-38-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.11-0ubuntu27.3
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: Unity:Unity7:ubuntu
Date: Sun Jun 14 12:38:14 2020
EcryptfsInUse: Yes
InstallationDate: Installed on 2012-03-23 (3004 days ago)
InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012)
SourcePackage: gnome-software
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: gnome-software (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug focal

** Attachment added: "Selection_670.png"
   
https://bugs.launchpad.net/bugs/1883421/+attachment/5383749/+files/Selection_670.png

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1883421

Title:
  Ubuntu Software can't install .deb files

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1883421/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1878338] Re: Laptop freezes whenever it runs out of battery

2020-05-28 Thread Vadim Peretokin
It suspended.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1878338

Title:
  Laptop freezes whenever it runs out of battery

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1878338/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1880095] Re: Keyboard entry stopped working

2020-05-22 Thread Vadim Peretokin
Yes the mouse did work, and I was able to use the Super key to bring up
Unity's application menu (on this computer I use Unity). Typing text
didn't work, though.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1880095

Title:
  Keyboard entry stopped working

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/compiz/+bug/1880095/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1880095] [NEW] Keyboard entry stopped working

2020-05-22 Thread Vadim Peretokin
Public bug reported:

I was toggling between text entry languages when the keyboard entry
suddenly stopped working. Even the onscreen keyboard was not able to
entry any keys.

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: xserver-xorg-input-all (not installed)
ProcVersionSignature: Ubuntu 5.4.0-31.35-generic 5.4.34
Uname: Linux 5.4.0-31-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
.proc.driver.nvidia.gpus..07.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:07: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-10ubuntu2)
.tmp.unity_support_test.0:
 
ApportVersion: 2.20.11-0ubuntu27
Architecture: amd64
BootLog:
 
CasperMD5CheckResult: skip
CompizPlugins: 
[core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,unitymtgrabhandles,workarounds,scale,expo,ezoom,unityshell]
CompositorRunning: compiz
CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
CompositorUnredirectFSW: true
CurrentDesktop: Unity:Unity7:ubuntu
Date: Fri May 22 09:18:07 2020
DistUpgraded: Fresh install
DistroCodename: focal
DistroVariant: ubuntu
DkmsStatus: nvidia, 435.21, 5.4.0-31-generic, x86_64: installed
EcryptfsInUse: Yes
ExtraDebuggingInterest: Yes
GraphicsCard:
 NVIDIA Corporation GP104 [GeForce GTX 1080] [10de:1b80] (rev a1) (prog-if 00 
[VGA controller])
   Subsystem: Micro-Star International Co., Ltd. [MSI] GP104 [GeForce GTX 1080] 
[1462:3362]
InstallationDate: Installed on 2012-03-23 (2981 days ago)
InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012)
MachineType: Gigabyte Technology Co., Ltd. X570 AORUS ELITE
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-31-generic 
root=UUID=20aa0109-67bb-46a0-95c6-626f0f0487eb ro quiet splash vt.handoff=7
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 12/06/2019
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: F11
dmi.board.asset.tag: Default string
dmi.board.name: X570 AORUS ELITE
dmi.board.vendor: Gigabyte Technology Co., Ltd.
dmi.board.version: x.x
dmi.chassis.asset.tag: Default string
dmi.chassis.type: 3
dmi.chassis.vendor: Default string
dmi.chassis.version: Default string
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF11:bd12/06/2019:svnGigabyteTechnologyCo.,Ltd.:pnX570AORUSELITE:pvr-CF:rvnGigabyteTechnologyCo.,Ltd.:rnX570AORUSELITE:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring:
dmi.product.family: Default string
dmi.product.name: X570 AORUS ELITE
dmi.product.sku: Default string
dmi.product.version: -CF
dmi.sys.vendor: Gigabyte Technology Co., Ltd.
version.compiz: compiz 1:0.9.14.1+20.04.20200211-0ubuntu1
version.libdrm2: libdrm2 2.4.101-2
version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1
version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.4-2ubuntu1
version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.6-1
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200226-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1
xserver.bootTime: Fri May 22 09:13:46 2020
xserver.configfile: default
xserver.errors:
 
xserver.logfile: /var/log/Xorg.0.log
xserver.outputs:
 
xserver.version: 2:1.20.8-2ubuntu2

** Affects: xorg (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug compiz-0.9 focal possible-manual-nvidia-install ubuntu

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1880095

Title:
  Keyboard entry stopped working

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1880095/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1879613] Re: Computer hung when resuming from suspend

2020-05-21 Thread Vadim Peretokin
No that's gone now. Anywhere in the logs they would be written?

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1879613

Title:
  Computer hung when resuming from suspend

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1879613/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1879613] Re: Computer hung when resuming from suspend

2020-05-21 Thread Vadim Peretokin
Where would they be?

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1879613

Title:
  Computer hung when resuming from suspend

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1879613/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1879664] [NEW] Reading mode missing from indicator

2020-05-20 Thread Vadim Peretokin
Public bug reported:

The 'Reading mode' option is missing from the indicator in Ubuntu 20.04.
Attached a screenshot.

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: workrave 1.10.37-1
ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30
Uname: Linux 5.4.0-29-generic x86_64
ApportVersion: 2.20.11-0ubuntu27
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Wed May 20 11:31:52 2020
EcryptfsInUse: Yes
InstallationDate: Installed on 2017-02-15 (1189 days ago)
InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719)
SourcePackage: workrave
UpgradeStatus: Upgraded to focal on 2020-05-07 (12 days ago)

** Affects: workrave (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug focal

** Attachment added: "Workspace 1_128.png"
   
https://bugs.launchpad.net/bugs/1879664/+attachment/5374628/+files/Workspace%201_128.png

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1879664

Title:
  Reading mode missing from indicator

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/workrave/+bug/1879664/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1879613] [NEW] Computer hung when resuming from suspend

2020-05-19 Thread Vadim Peretokin
Public bug reported:

The computer seemingly hung when resuming from suspend and failed to
show the login screen. Switching to Ctr+Alt+F2 was showing a lot of disk
errors.

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: linux-image-5.4.0-31-generic 5.4.0-31.35
ProcVersionSignature: Ubuntu 5.4.0-31.35-generic 5.4.34
Uname: Linux 5.4.0-31-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.11-0ubuntu27
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  vadi   3100 F pulseaudio
 /dev/snd/controlC1:  vadi   3100 F pulseaudio
CasperMD5CheckResult: skip
CurrentDesktop: Unity:Unity7:ubuntu
Date: Wed May 20 07:01:51 2020
EcryptfsInUse: Yes
InstallationDate: Installed on 2012-03-23 (2979 days ago)
InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012)
MachineType: Gigabyte Technology Co., Ltd. X570 AORUS ELITE
ProcFB: 0 VESA VGA
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-31-generic 
root=UUID=20aa0109-67bb-46a0-95c6-626f0f0487eb ro quiet splash vt.handoff=7
RelatedPackageVersions:
 linux-restricted-modules-5.4.0-31-generic N/A
 linux-backports-modules-5.4.0-31-generic  N/A
 linux-firmware1.187
RfKill:
 
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 12/06/2019
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: F11
dmi.board.asset.tag: Default string
dmi.board.name: X570 AORUS ELITE
dmi.board.vendor: Gigabyte Technology Co., Ltd.
dmi.board.version: x.x
dmi.chassis.asset.tag: Default string
dmi.chassis.type: 3
dmi.chassis.vendor: Default string
dmi.chassis.version: Default string
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF11:bd12/06/2019:svnGigabyteTechnologyCo.,Ltd.:pnX570AORUSELITE:pvr-CF:rvnGigabyteTechnologyCo.,Ltd.:rnX570AORUSELITE:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring:
dmi.product.family: Default string
dmi.product.name: X570 AORUS ELITE
dmi.product.sku: Default string
dmi.product.version: -CF
dmi.sys.vendor: Gigabyte Technology Co., Ltd.

** Affects: linux (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug focal

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1879613

Title:
  Computer hung when resuming from suspend

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1879613/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1878395] [NEW] Gnome-software spammed log files with 3, 000 lines

2020-05-13 Thread Vadim Peretokin
Public bug reported:

Gnome-software spammed log files with 3,000 lines of text and that's not
OK.

ProblemType: Bug
DistroRelease: Ubuntu 19.10
Package: gnome-software 3.30.6-2ubuntu10.19.10.1
ProcVersionSignature: Ubuntu 5.3.0-52.46-generic 5.3.18
Uname: Linux 5.3.0-52-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.11-0ubuntu8.8
Architecture: amd64
CurrentDesktop: Unity:Unity7:ubuntu
Date: Wed May 13 12:56:19 2020
EcryptfsInUse: Yes
InstallationDate: Installed on 2012-03-23 (2972 days ago)
InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012)
InstalledPlugins:
 gnome-software-plugin-flatpak 3.30.6-2ubuntu10.19.10.1
 gnome-software-plugin-snap3.30.6-2ubuntu10.19.10.1
SourcePackage: gnome-software
UpgradeStatus: Upgraded to eoan on 2019-11-07 (187 days ago)

** Affects: gnome-software (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug eoan third-party-packages

** Attachment added: "gnome-software spam"
   
https://bugs.launchpad.net/bugs/1878395/+attachment/5370889/+files/gnome-software%20spam

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1878395

Title:
  Gnome-software spammed log files with 3,000 lines

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1878395/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1878338] [NEW] Laptop freezes whenever it runs out of battery

2020-05-12 Thread Vadim Peretokin
Public bug reported:

New behaviour for Ubuntu 20.04 LTS - as soon as it runs out of battery,
the laptop locks up. Any audio that was playing will be played
repeatedly on a short loop.

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: linux-image-5.4.0-29-generic 5.4.0-29.33
ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30
Uname: Linux 5.4.0-29-generic x86_64
ApportVersion: 2.20.11-0ubuntu27
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  vadi   3163 F pulseaudio
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Wed May 13 07:40:48 2020
EcryptfsInUse: Yes
HibernationDevice: RESUME=UUID=8c0e25d4-6e36-428e-b354-4c71b99db752
InstallationDate: Installed on 2017-02-15 (1182 days ago)
InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719)
MachineType: Dell Inc. Latitude E7470
ProcFB: 0 i915drmfb
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-29-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
RelatedPackageVersions:
 linux-restricted-modules-5.4.0-29-generic N/A
 linux-backports-modules-5.4.0-29-generic  N/A
 linux-firmware1.187
SourcePackage: linux
UpgradeStatus: Upgraded to focal on 2020-05-07 (5 days ago)
dmi.bios.date: 10/08/2019
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 1.22.8
dmi.board.name: 0T6HHJ
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 9
dmi.chassis.vendor: Dell Inc.
dmi.modalias: 
dmi:bvnDellInc.:bvr1.22.8:bd10/08/2019:svnDellInc.:pnLatitudeE7470:pvr:rvnDellInc.:rn0T6HHJ:rvrA00:cvnDellInc.:ct9:cvr:
dmi.product.family: Latitude
dmi.product.name: Latitude E7470
dmi.product.sku: 06DC
dmi.sys.vendor: Dell Inc.

** Affects: linux (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug focal

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1878338

Title:
  Laptop freezes whenever it runs out of battery

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1878338/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1877712] Re: Severe performance degradation in Gnome Shell after upgrade to 20.04

2020-05-11 Thread Vadim Peretokin
Sorry, that's not really practical to do on a production system.

That said, the issue could have been because there wasn't enough disk
space. Clearing it up and rebooting seems to have solved things. This is
a change in behaviour from previous Ubuntu releases.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1877712

Title:
  Severe performance degradation in Gnome Shell after upgrade to 20.04

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1877712/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1877712] Re: Severe performance degradation in Gnome Shell after upgrade to 20.04

2020-05-09 Thread Vadim Peretokin
The log file is absolutely flooded with errors like:

May  9 08:53:48 volga gnome-shell[3395]: Attempting to call back into JSAPI 
during the sweeping phase of GC. This is most likely caused by not destroying a 
Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be 
caused by using the destroy(), dispose(), or remove() vfuncs. Because it would 
crash the application, it has been blocked and the JS callback not invoked.
May  9 08:53:48 volga gnome-shell[3395]: The offending signal was notify on 
MetaDisplay 0x555ad20ba000.
May  9 08:53:48 volga gnome-shell[3395]: Attempting to call back into JSAPI 
during the sweeping phase of GC. This is most likely caused by not destroying a 
Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be 
caused by using the destroy(), dispose(), or remove() vfuncs. Because it would 
crash the application, it has been blocked and the JS callback not invoked.
May  9 08:53:48 volga gnome-shell[3395]: The offending signal was notify on 
MetaDisplay 0x555ad20ba000.
May  9 08:53:48 volga gnome-shell[3395]: Attempting to call back into JSAPI 
during the sweeping phase of GC. This is most likely caused by not destroying a 
Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be 
caused by using the destroy(), dispose(), or remove() vfuncs. Because it would 
crash the application, it has been blocked and the JS callback not invoked.
May  9 08:53:48 volga gnome-shell[3395]: The offending signal was notify on 
MetaDisplay 0x555ad20ba000.
May  9 08:53:48 volga gnome-shell[3395]: Attempting to call back into JSAPI 
during the sweeping phase of GC. This is most likely caused by not destroying a 
Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be 
caused by using the destroy(), dispose(), or remove() vfuncs. Because it would 
crash the application, it has been blocked and the JS callback not invoked.
May  9 08:53:48 volga gnome-shell[3395]: The offending signal was notify on 
MetaDisplay 0x555ad20ba000.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1877712

Title:
  Severe performance degradation in Gnome Shell after upgrade to 20.04

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1877712/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1877712] [NEW] Severe performance degradation in Gnome Shell after upgrade to 20.04

2020-05-09 Thread Vadim Peretokin
Public bug reported:

Severe performance degradation in Gnome Shell after upgrade to 20.04 -
everything is slow, even moving the mouse through a right-click menu has
a severely delayed selection animation.

Video displaying the problem: https://drive.google.com/open?id=1rAKN-
ZKks6o9d37hQMbnMgNeAOy8VZyp

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: gnome-shell 3.36.1-5ubuntu1
ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30
Uname: Linux 5.4.0-29-generic x86_64
ApportVersion: 2.20.11-0ubuntu27
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Sat May  9 08:57:02 2020
DisplayManager: lightdm
EcryptfsInUse: Yes
InstallationDate: Installed on 2017-02-15 (1178 days ago)
InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719)
RelatedPackageVersions: mutter-common 3.36.1-3ubuntu3
SourcePackage: gnome-shell
UpgradeStatus: Upgraded to focal on 2020-05-07 (1 days ago)

** Affects: gnome-shell (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug focal

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1877712

Title:
  Severe performance degradation in Gnome Shell after upgrade to 20.04

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1877712/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1865975] Re: Blank 'Updates' screen

2020-03-23 Thread Vadim Peretokin
It showed an error message this time around - attached screenshot.

** Attachment added: "Selection_211.png"
   
https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1865975/+attachment/5340339/+files/Selection_211.png

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1865975

Title:
  Blank 'Updates' screen

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1865975/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1865975] Re: Blank 'Updates' screen

2020-03-23 Thread Vadim Peretokin
Hi! Attached is the log of when it happened again.

** Attachment added: "log.txt"
   
https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1865975/+attachment/5340338/+files/log.txt

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1865975

Title:
  Blank 'Updates' screen

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1865975/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1867758] Re: Gnome shell froze completely

2020-03-19 Thread Vadim Peretokin
1. _usr_bin_gnome-screensaver crashed on the 16th, which is a day before
this report. That crash was uploaded. _usr_bin_gnome-shell.1000 also
crashes on the 11th, that was uploaded as well.

2. I've uninstalled everything I could, will see if it happens again. I
just had the freeze happen now while extensions were still installed.

** Attachment added: "Screenshot_2020-03-19 Installed Extensions - GNOME Shell 
Extensions.png"
   
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1867758/+attachment/5338729/+files/Screenshot_2020-03-19%20Installed%20Extensions%20-%20GNOME%20Shell%20Extensions.png

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1867758

Title:
  Gnome shell froze completely

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1867758/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1867758] Re: Gnome shell froze completely

2020-03-17 Thread Vadim Peretokin
Attached is a video of what happened:
https://bugs.launchpad.net/ubuntu/+source/gnome-
shell/+bug/1867758/+attachment/5337919/+files/Gnome%20Shell%20freeze.mp4

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1867758

Title:
  Gnome shell froze completely

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1867758/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1867758] [NEW] Gnome shell froze completely

2020-03-17 Thread Vadim Peretokin
Public bug reported:

Gnome shell froze completely and would not respond to any mouse clicks
or keyboard action. The mouse did move, but that's about it. It stayed
this way for ~15mins before I reset it and lost all my work.

ProblemType: Bug
DistroRelease: Ubuntu 19.10
Package: gnome-shell 3.34.1+git20191024-1ubuntu1~19.10.1
ProcVersionSignature: Ubuntu 5.3.0-40.32-generic 5.3.18
Uname: Linux 5.3.0-40-generic x86_64
ApportVersion: 2.20.11-0ubuntu8.4
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Tue Mar 17 11:51:50 2020
DisplayManager: lightdm
EcryptfsInUse: Yes
InstallationDate: Installed on 2017-02-15 (1126 days ago)
InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719)
RelatedPackageVersions: mutter-common 3.34.1+git20191107-1ubuntu1~19.10.1
SourcePackage: gnome-shell
UpgradeStatus: Upgraded to eoan on 2020-02-15 (30 days ago)

** Affects: gnome-shell (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug eoan

** Attachment added: "Gnome Shell freeze.mp4"
   
https://bugs.launchpad.net/bugs/1867758/+attachment/5337919/+files/Gnome%20Shell%20freeze.mp4

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1867758

Title:
  Gnome shell froze completely

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1867758/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1866004] Re: Correct password does not unlock computer

2020-03-04 Thread Vadim Peretokin
Right-clicking on the password field doesn't show me a menu :(

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1866004

Title:
  Correct password does not unlock computer

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1866004/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1866004] [NEW] Correct password does not unlock computer

2020-03-04 Thread Vadim Peretokin
Public bug reported:

Every once in a while the lock screen will stop accepting the correct
password, and I lose all my open work.

I do have two input methods installed, but toggling between them on the
lock screen does not work.

I am able to go back to the main login screen and enter the password
there, but then it simply takes me back to the lock screen.

Happy to add any additional information!

ProblemType: Bug
DistroRelease: Ubuntu 19.10
Package: gnome-shell 3.34.1+git20191024-1ubuntu1~19.10.1
ProcVersionSignature: Ubuntu 5.3.0-40.32-generic 5.3.18
Uname: Linux 5.3.0-40-generic x86_64
ApportVersion: 2.20.11-0ubuntu8.4
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Wed Mar  4 09:46:22 2020
DisplayManager: lightdm
EcryptfsInUse: Yes
InstallationDate: Installed on 2017-02-15 (1112 days ago)
InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719)
RelatedPackageVersions: mutter-common 3.34.1+git20191107-1ubuntu1~19.10.1
SourcePackage: gnome-shell
UpgradeStatus: Upgraded to eoan on 2020-02-15 (17 days ago)

** Affects: gnome-shell (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug eoan

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1866004

Title:
  Correct password does not unlock computer

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1866004/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1865975] [NEW] Blank 'Updates' screen

2020-03-03 Thread Vadim Peretokin
Public bug reported:

The software updater keeps interrupting me with "updates available" and
then shows me a blank screen.

ProblemType: Bug
DistroRelease: Ubuntu 19.10
Package: gnome-software 3.30.6-2ubuntu10.19.10.0
ProcVersionSignature: Ubuntu 5.3.0-40.32-generic 5.3.18
Uname: Linux 5.3.0-40-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.11-0ubuntu8.4
Architecture: amd64
CurrentDesktop: Unity:Unity7:ubuntu
Date: Wed Mar  4 06:40:21 2020
EcryptfsInUse: Yes
InstallationDate: Installed on 2012-03-23 (2902 days ago)
InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012)
InstalledPlugins:
 gnome-software-plugin-flatpak 3.30.6-2ubuntu10.19.10.0
 gnome-software-plugin-snap3.30.6-2ubuntu10.19.10.0
SourcePackage: gnome-software
UpgradeStatus: Upgraded to eoan on 2019-11-07 (117 days ago)

** Affects: gnome-software (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug eoan third-party-packages

** Attachment added: "Selection_450.png"
   
https://bugs.launchpad.net/bugs/1865975/+attachment/5333259/+files/Selection_450.png

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1865975

Title:
  Blank 'Updates' screen

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1865975/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1856648] [NEW] Software centre display is blank

2019-12-16 Thread Vadim Peretokin
Public bug reported:

Software centre disrupts my workflow with an urgent notification for
"important" updates, yet when I click 'View', it shows nothing.

ProblemType: Bug
DistroRelease: Ubuntu 19.10
Package: gnome-software 3.30.6-2ubuntu10.19.10.0
ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10
Uname: Linux 5.3.0-24-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.11-0ubuntu8.2
Architecture: amd64
CurrentDesktop: Unity:Unity7:ubuntu
Date: Tue Dec 17 06:27:49 2019
EcryptfsInUse: Yes
InstallationDate: Installed on 2012-03-23 (2824 days ago)
InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012)
InstalledPlugins:
 gnome-software-plugin-flatpak 3.30.6-2ubuntu10.19.10.0
 gnome-software-plugin-snap3.30.6-2ubuntu10.19.10.0
SourcePackage: gnome-software
UpgradeStatus: Upgraded to eoan on 2019-11-07 (39 days ago)

** Affects: gnome-software (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug eoan third-party-packages

** Attachment added: "2019-12-17_06-28.png"
   
https://bugs.launchpad.net/bugs/1856648/+attachment/5313155/+files/2019-12-17_06-28.png

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1856648

Title:
  Software centre display is blank

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1856648/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Re: [Bug 1502263] Re: Shutter does not work in Wayland

2019-05-16 Thread Vadim Peretokin
Not yet - need someone to step up to do the work.

On Thu, 16 May 2019, 4:55 pm theo, <1502...@bugs.launchpad.net> wrote:

> Same issue on ubuntu 18.04.
> Any news ?
>
> --
> You received this bug notification because you are a member of Shutter
> Team, which is subscribed to shutter in Ubuntu.
> https://bugs.launchpad.net/bugs/1502263
>
> Title:
>   Shutter does not work in Wayland
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/shutter/+bug/1502263/+subscriptions
>

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1502263

Title:
  Shutter does not work in Wayland

To manage notifications about this bug go to:
https://bugs.launchpad.net/shutter/+bug/1502263/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1772355] [NEW] Clicking on Total War: Attila does not bring up the window

2018-05-20 Thread Vadim Peretokin
Public bug reported:

Clicking on Total War: Attila does not bring up the window; instead it
opens the window selection menu - and when you move your mouse over the
window icon, it goes into drag mode. See attached screencast for a
demonstration.

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: gnome-shell-extension-ubuntu-dock 0.9.1
ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
Uname: Linux 4.15.0-20-generic x86_64
NonfreeKernelModules: vtsspp sep4_1 socperf2_0 pax nvidia_modeset nvidia
ApportVersion: 2.20.9-0ubuntu7
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Mon May 21 07:20:00 2018
EcryptfsInUse: Yes
InstallationDate: Installed on 2012-03-23 (2249 days ago)
InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012)
PackageArchitecture: all
SourcePackage: gnome-shell-extension-ubuntu-dock
UpgradeStatus: Upgraded to bionic on 2018-05-13 (7 days ago)

** Affects: gnome-shell-extension-ubuntu-dock (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug bionic

** Attachment added: "Screencast_21-05-18_07:10:12.webm"
   
https://bugs.launchpad.net/bugs/1772355/+attachment/5142143/+files/Screencast_21-05-18_07%3A10%3A12.webm

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1772355

Title:
  Clicking on Total War: Attila does not bring up the window

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-ubuntu-dock/+bug/1772355/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1765261] Re: [regression] Ubuntu 18.04 login screen rejects a valid password on first attempt. Usually works on the second attempt

2018-05-18 Thread Vadim Peretokin
Sorry but this bug report is not for discussion on the best flavour of
Ubuntu - please ask on the forums and don't spam everyone involved in
the discussion.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1765261

Title:
  [regression] Ubuntu 18.04 login screen rejects a valid password on
  first attempt. Usually works on the second attempt

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1765261/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1765261] Re: [regression] Ubuntu 18.04 login screen rejects a valid password on first attempt. Usually works on the second attempt

2018-05-17 Thread Vadim Peretokin
Second time does not work for me - neither the third, nor the tenth.
Once I lock the screen, there is a chance the GNOME environment will
reject all password attempts to lock it and I have to lose all my work
by forcing a restart. This is a very serious problem.

Is there a workaround available?

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1765261

Title:
  [regression] Ubuntu 18.04 login screen rejects a valid password on
  first attempt. Usually works on the second attempt

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1765261/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Re: [Bug 1765726] Re: Optional dependencies are missing for Shutter in Ubuntu 18.04

2018-05-14 Thread Vadim Peretokin
That would be great Photon. I rely on Shutter as there are no good
alternatives that stand up in functionality.

On Mon, May 14, 2018 at 5:55 PM Photon  wrote:

> Thanks for clarification! Still, this is important information.
>
> To give everybody an update: I asked for support at the snapcraft.io
> forums, however got no reply at some point (maybe my questions were
> stupid, that is, indicated lack of research effort, but I had no time to
> learn everything by myself back then). I will try to revive the topic
> now and see if I can creat a snap eventually...
>
> --
> You received this bug notification because you are a member of Shutter
> Team, which is subscribed to shutter in Ubuntu.
> https://bugs.launchpad.net/bugs/1765726
>
> Title:
>   Optional dependencies are missing for Shutter in Ubuntu 18.04
>
> To manage notifications about this bug go to:
>
> https://bugs.launchpad.net/ubuntu/+source/libgoo-canvas-perl/+bug/1765726/+subscriptions
>

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1765726

Title:
  Optional dependencies are missing for Shutter in Ubuntu 18.04

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libgoo-canvas-perl/+bug/1765726/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1771068] [NEW] package libsane1 1.0.27-1~experimental2ubuntu2.1 failed to install/upgrade: trying to overwrite shared '/lib/udev/hwdb.d/20-sane.hwdb', which is different from other instances of p

2018-05-14 Thread Vadim Peretokin
Public bug reported:

Trying to install winehq-staging from the Wine APT repository on Ubuntu
17.10 yields this error.

ProblemType: Package
DistroRelease: Ubuntu 17.10
Package: libsane1 1.0.27-1~experimental2ubuntu2.1
ProcVersionSignature: Ubuntu 4.13.0-42.47-generic 4.13.16
Uname: Linux 4.13.0-42-generic x86_64
NonfreeKernelModules: sep4_1 socperf2_0 pax
ApportVersion: 2.20.7-0ubuntu3.8
Architecture: amd64
Date: Mon May 14 09:25:17 2018
DuplicateSignature:
 package:libsane1:1.0.27-1~experimental2ubuntu2.1
 Unpacking libsane1:i386 (1.0.27-1~experimental2ubuntu2.1) ...
 dpkg: error processing archive 
/tmp/apt-dpkg-install-va4Lad/20-libsane1_1.0.27-1~experimental2ubuntu2.1_i386.deb
 (--unpack):
  trying to overwrite shared '/lib/udev/hwdb.d/20-sane.hwdb', which is 
different from other instances of package libsane1:i386
ErrorMessage: trying to overwrite shared '/lib/udev/hwdb.d/20-sane.hwdb', which 
is different from other instances of package libsane1:i386
InstallationDate: Installed on 2017-02-15 (452 days ago)
InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719)
Python3Details: /usr/bin/python3.6, Python 3.6.3, python3-minimal, 
3.6.3-0ubuntu2
PythonDetails: /usr/bin/python2.7, Python 2.7.14, python-minimal, 
2.7.14-2ubuntu1
RelatedPackageVersions:
 dpkg 1.18.24ubuntu1
 apt  1.5.1
SourcePackage: sane-backends
Title: package libsane1 1.0.27-1~experimental2ubuntu2.1 failed to 
install/upgrade: trying to overwrite shared '/lib/udev/hwdb.d/20-sane.hwdb', 
which is different from other instances of package libsane1:i386
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: sane-backends (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-package artful package-conflict

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1771068

Title:
  package libsane1 1.0.27-1~experimental2ubuntu2.1 failed to
  install/upgrade: trying to overwrite shared
  '/lib/udev/hwdb.d/20-sane.hwdb', which is different from other
  instances of package libsane1:i386

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/sane-backends/+bug/1771068/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1769298] [NEW] Unlock screen does not accept correct password

2018-05-04 Thread Vadim Peretokin
Public bug reported:

The unlock screen that you get after locking the computer will sometimes
not accept the correct password. If I switch to tty1 I can login with
the same, correct password fine and if I reboot the computer (lose all
my open apps and unsaved data), the password works fine as well.

ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: gnome-shell 3.26.2-0ubuntu0.1
ProcVersionSignature: Ubuntu 4.13.0-39.44-generic 4.13.16
Uname: Linux 4.13.0-39-generic x86_64
NonfreeKernelModules: sep4_1 socperf2_0 pax nvidia_uvm nvidia_drm 
nvidia_modeset nvidia
ApportVersion: 2.20.7-0ubuntu3.8
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Sat May  5 07:11:57 2018
DisplayManager: lightdm
EcryptfsInUse: Yes
InstallationDate: Installed on 2012-03-23 (2233 days ago)
InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012)
SourcePackage: gnome-shell
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: gnome-shell (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug artful

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1769298

Title:
  Unlock screen does not accept correct password

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1769298/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1739928] Re: Kernel segfault playing EVERSPACE

2017-12-24 Thread Vadim Peretokin
What would be the problem?

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1739928

Title:
  Kernel segfault playing EVERSPACE

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1739928/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1739928] [NEW] Kernel segfault playing EVERSPACE

2017-12-23 Thread Vadim Peretokin
Public bug reported:

Here is the stacktrace: https://paste.ubuntu.com/26240799

ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: linux-image-4.13.0-21-generic 4.13.0-21.24
ProcVersionSignature: Ubuntu 4.13.0-21.24-generic 4.13.13
Uname: Linux 4.13.0-21-generic x86_64
NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
ApportVersion: 2.20.7-0ubuntu3.6
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC1:  vadi   7458 F pulseaudio
 /dev/snd/controlC0:  vadi   7458 F pulseaudio
CurrentDesktop: Unity:Unity7:ubuntu
Date: Sun Dec 24 03:47:54 2017
EcryptfsInUse: Yes
InstallationDate: Installed on 2012-03-23 (2101 days ago)
InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012)
MachineType: Gigabyte Technology Co., Ltd. Z68AP-D3
ProcFB:
 0 VESA VGA
 1 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-21-generic 
root=UUID=20aa0109-67bb-46a0-95c6-626f0f0487eb ro quiet splash vt.handoff=7
RelatedPackageVersions:
 linux-restricted-modules-4.13.0-21-generic N/A
 linux-backports-modules-4.13.0-21-generic  N/A
 linux-firmware 1.169.1
RfKill:
 0: phy0: Wireless LAN
Soft blocked: yes
Hard blocked: no
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 10/12/2011
dmi.bios.vendor: Award Software International, Inc.
dmi.bios.version: FB
dmi.board.name: Z68AP-D3
dmi.board.vendor: Gigabyte Technology Co., Ltd.
dmi.board.version: x.x
dmi.chassis.type: 3
dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
dmi.modalias: 
dmi:bvnAwardSoftwareInternational,Inc.:bvrFB:bd10/12/2011:svnGigabyteTechnologyCo.,Ltd.:pnZ68AP-D3:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnZ68AP-D3:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr:
dmi.product.name: Z68AP-D3
dmi.sys.vendor: Gigabyte Technology Co., Ltd.

** Affects: linux (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug artful

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1739928

Title:
  Kernel segfault playing EVERSPACE

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1739928/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1670586] Re: /usr/games/mudlet:11:QExplicitlySharedDataPointer:QNetworkConfiguration::~QNetworkConfiguration:QHashData::free_helper:QHash:QHash

2017-12-16 Thread Vadim Peretokin
** Changed in: mudlet (Ubuntu)
   Status: Incomplete => Fix Released

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1670586

Title:
  
/usr/games/mudlet:11:QExplicitlySharedDataPointer:QNetworkConfiguration::~QNetworkConfiguration:QHashData::free_helper:QHash:QHash

To manage notifications about this bug go to:
https://bugs.launchpad.net/mudlet/+bug/1670586/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1735666] [NEW] package libsane1 1.0.27-1~experimental2ubuntu2.1 failed to install/upgrade: trying to overwrite shared '/lib/udev/hwdb.d/20-sane.hwdb', which is different from other instances of p

2017-11-30 Thread Vadim Peretokin
Public bug reported:

This popped up out of the blue.

ProblemType: Package
DistroRelease: Ubuntu 17.10
Package: libsane1 1.0.27-1~experimental2ubuntu2.1
ProcVersionSignature: Ubuntu 4.13.0-17.20-generic 4.13.8
Uname: Linux 4.13.0-17-generic x86_64
NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
ApportVersion: 2.20.7-0ubuntu3.5
Architecture: amd64
Date: Thu Nov 23 10:10:49 2017
DuplicateSignature:
 package:libsane1:1.0.27-1~experimental2ubuntu2.1
 Unpacking libsane1:i386 (1.0.27-1~experimental2ubuntu2.1) ...
 dpkg: error processing archive 
/tmp/apt-dpkg-install-tBrFZ4/52-libsane1_1.0.27-1~experimental2ubuntu2.1_i386.deb
 (--unpack):
  trying to overwrite shared '/lib/udev/hwdb.d/20-sane.hwdb', which is 
different from other instances of package libsane1:i386
ErrorMessage: trying to overwrite shared '/lib/udev/hwdb.d/20-sane.hwdb', which 
is different from other instances of package libsane1:i386
InstallationDate: Installed on 2012-03-23 (2078 days ago)
InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012)
Python3Details: /usr/bin/python3.6, Python 3.6.3, python3-minimal, 
3.6.3-0ubuntu2
PythonDetails: /usr/bin/python2.7, Python 2.7.14, python-minimal, 
2.7.14-2ubuntu1
RelatedPackageVersions:
 dpkg 1.18.24ubuntu1
 apt  1.5.1
SourcePackage: sane-backends
Title: package libsane1 1.0.27-1~experimental2ubuntu2.1 failed to 
install/upgrade: trying to overwrite shared '/lib/udev/hwdb.d/20-sane.hwdb', 
which is different from other instances of package libsane1:i386
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: sane-backends (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-package artful package-conflict

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1735666

Title:
  package libsane1 1.0.27-1~experimental2ubuntu2.1 failed to
  install/upgrade: trying to overwrite shared
  '/lib/udev/hwdb.d/20-sane.hwdb', which is different from other
  instances of package libsane1:i386

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/sane-backends/+bug/1735666/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1724564] Re: Cannot enter password to unlock encryption in 4.10

2017-11-06 Thread Vadim Peretokin
It either worked then or I booted the wrong kernel. 4.10.0-38 and
today's 4.10.0-39 are not working, so I am back to using in
4.9.45-040945 order to be able to access the machine.

** Changed in: linux (Ubuntu)
   Status: Fix Committed => New

** Changed in: linux (Ubuntu Zesty)
   Status: Fix Committed => New

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1724564

Title:
  Cannot enter password to unlock encryption in 4.10

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1724564/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Re: [Bug 1705369] Re: Ubuntu 17.10 boots to black screen when using Nvidia drivers (on a desktop with an Intel GPU)

2017-11-05 Thread Vadim Peretokin
You can also do all of the commands from the rescue mode.

What is concerning is that this major issue is still left untouched. Is
there anything we can do to help?

On Sun, 5 Nov 2017, 10:05 pm William Haverstock, 
wrote:

> I had the blank screen, no login screen problem.
>
> The computer was otherwise running though.
>
> I ssh-ed from another computer to the problem computer
> to execute the suggested commands.
>
> If on a home network you can login to your router with a
> web browser to get the IP address for your problem computer.
>
> Mine was 192.168.1.3
>
> The following fixed the problem for me.
>
> First I did (without the comment).
>
>   sudo apt-get install lightdm # This showed lightdm was installed
>
> Second I did uname -r and found the completion for
> the linux-headers-$(uname -r) command.
>
> I don't know why I didn't use the suggested:
> sudo apt install linux-headers-$(uname -r)
>
> Then I did the suggested commands, one after the other:
>   sudo apt purge gdm3
>   sudo apt purge nvidia*
>   sudo apt install linux-headers-4.13.0-16-generic # ADJUST THIS
>   sudo apt install nvidia-384
>   sudo dpkg-reconfigure lightdm # Suggested when 1st command ran
>   sudo shutdown -r now  # Restart
>
> Went to the problem computer, the login screen came up.
>
> The Desktop Environment that was selected was:
>   Ubuntu on Xorg(Default)
>
> I was able to login.
>
> My problem computer is at least 10 years old.
>
> --
> You received this bug notification because you are subscribed to a
> duplicate bug report (1726425).
> https://bugs.launchpad.net/bugs/1705369
>
> Title:
>   Ubuntu 17.10 boots to black screen when using Nvidia drivers (on a
>   desktop with an Intel GPU)
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1705369/+subscriptions
>

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1705369

Title:
  Ubuntu 17.10 boots to black screen when using Nvidia drivers (on a
  desktop with an Intel GPU)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1705369/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Re: [Bug 1705369] Re: Ubuntu 17.10 boots to black screen when using Nvidia drivers (on a desktop with an Intel GPU)

2017-11-04 Thread Vadim Peretokin
Hmm. What I did was load into recovery mode which allowed me to install and
uninstall packages - there I uninstalled lightgdm and ran the suggested
dpkg-config command to setup gdm.

On Sat, Nov 4, 2017 at 4:11 PM Bernadette Addison 
wrote:

> none of the workarounds or suggestions here work for me.  It is an
> impossible task getting nvidia drivers to work even when only using
> XORG/ X11 services and NOT wayland.  I will keep looking for answers...
>
> --
> You received this bug notification because you are subscribed to a
> duplicate bug report (1726425).
> https://bugs.launchpad.net/bugs/1705369
>
> Title:
>   Ubuntu 17.10 boots to black screen when using Nvidia drivers (on a
>   desktop with an Intel GPU)
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1705369/+subscriptions
>

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1705369

Title:
  Ubuntu 17.10 boots to black screen when using Nvidia drivers (on a
  desktop with an Intel GPU)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1705369/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Re: [Bug 1502263] Re: Shutter does not work in Wayland

2017-11-04 Thread Vadim Peretokin
That sounds pretty disappointing that you are willing to negatively impact
a lot of users for a completely arbitrary reason as far as the end user is
concerned. The tool isn't great anymore and doesn't work on all setups, but
there are still ways to make it work and removing those ways will not add
any value whatsoever.

On Sat, Nov 4, 2017 at 8:46 AM Dominique Dumont 
wrote:

> Shutter has not been maintained for years and uses obsolete libraries.
> On Debian side, we are considering removing shutter from Debian despite
> its usefulness and popularity. See https://bugs.debian.org/cgi-
> bin/bugreport.cgi?bug=870418#54
>
> So, jerther, feel free to step in. I don't think anyone will complain if
> shutter gets a new active maintainer.
>
> Dod, on behalf of Debian-perl team
>
> ** Bug watch added: Debian Bug tracker #870418
>https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=870418
>
> --
> You received this bug notification because you are a member of Shutter
> Team, which is subscribed to shutter in Ubuntu.
> https://bugs.launchpad.net/bugs/1502263
>
> Title:
>   Shutter does not work in Wayland
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/shutter/+bug/1502263/+subscriptions
>

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1502263

Title:
  Shutter does not work in Wayland

To manage notifications about this bug go to:
https://bugs.launchpad.net/shutter/+bug/1502263/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Re: [Bug 1502263] Re: Shutter does not work in Wayland

2017-11-03 Thread Vadim Peretokin
That would be great.

On Fri, Nov 3, 2017 at 2:44 PM Timothy Zorn  wrote:

> I'll fix this eventually.
>
> I think the easiest solution is to detect if GNOME is being used and it
> so, check for gnome-screenshot. Then, grab screenshots via gnome-
> screenshot.
>
> --
> You received this bug notification because you are a member of Shutter
> Team, which is subscribed to shutter in Ubuntu.
> https://bugs.launchpad.net/bugs/1502263
>
> Title:
>   Shutter does not work in Wayland
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/shutter/+bug/1502263/+subscriptions
>

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1502263

Title:
  Shutter does not work in Wayland

To manage notifications about this bug go to:
https://bugs.launchpad.net/shutter/+bug/1502263/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Re: [Bug 1502263] Re: Shutter does not work in Wayland

2017-11-03 Thread Vadim Peretokin
Yeah, see the bug title. Shutter has not been actively maintained and
Wayland doesn't offer the same way of capturing an images - if there are
ways at all.

On Fri, Nov 3, 2017 at 2:25 PM Jerther <1502...@bugs.launchpad.net>
wrote:

> So the workaround is to not use Wayland... :(
>
> --
> You received this bug notification because you are a member of Shutter
> Team, which is subscribed to shutter in Ubuntu.
> https://bugs.launchpad.net/bugs/1502263
>
> Title:
>   Shutter does not work in Wayland
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/shutter/+bug/1502263/+subscriptions
>

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1502263

Title:
  Shutter does not work in Wayland

To manage notifications about this bug go to:
https://bugs.launchpad.net/shutter/+bug/1502263/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1728424] [NEW] Calendar is not respecting 12hour setting

2017-10-29 Thread Vadim Peretokin
Public bug reported:

I have Ubuntu set to show time as 12hours yet the calendar is using 24
hours, which is uncomfortable.

ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: gnome-calendar 3.26.2-1
ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
Uname: Linux 4.13.0-16-generic x86_64
NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
ApportVersion: 2.20.7-0ubuntu3.1
Architecture: amd64
CurrentDesktop: Unity:Unity7:ubuntu
Date: Sun Oct 29 14:53:21 2017
EcryptfsInUse: Yes
InstallationDate: Installed on 2012-03-23 (2045 days ago)
InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012)
SourcePackage: gnome-calendar
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: gnome-calendar (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug artful

** Attachment added: "Workspace 1_228.png"
   
https://bugs.launchpad.net/bugs/1728424/+attachment/4999556/+files/Workspace%201_228.png

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1728424

Title:
  Calendar is not respecting 12hour setting

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-calendar/+bug/1728424/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Re: [Bug 1705369] Re: Ubuntu 17.10 boots to black screen when using Nvidia drivers (on a desktop with an Intel GPU)

2017-10-29 Thread Vadim Peretokin
The VM would be using VirtualBox drivers, not NVIDIA - so I don't think
your problem is related!

On Sun, 29 Oct 2017, 4:45 pm CaptSaltyJack, <1705...@bugs.launchpad.net>
wrote:

> Thanks! Ran that on a VM as a test. I wound up with a text-based login
> shell, no greeter. "sudo apt install lightdm" fixed that, but my VM may
> not have been in a totally clean state.
>
> --
> You received this bug notification because you are subscribed to a
> duplicate bug report (1726425).
> https://bugs.launchpad.net/bugs/1705369
>
> Title:
>   Ubuntu 17.10 boots to black screen when using Nvidia drivers (on a
>   desktop with an Intel GPU)
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1705369/+subscriptions
>

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1705369

Title:
  Ubuntu 17.10 boots to black screen when using Nvidia drivers (on a
  desktop with an Intel GPU)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1705369/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1705369] Re: Ubuntu 17.10 boots to black screen when using Nvidia drivers (on a desktop with an Intel GPU)

2017-10-29 Thread Vadim Peretokin
sudo apt purge gdm3
sudo apt purge nvidia*
sudo apt install linux-headers-$(uname -r)
sudo apt install nvidia-384

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1705369

Title:
  Ubuntu 17.10 boots to black screen when using Nvidia drivers (on a
  desktop with an Intel GPU)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1705369/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Re: [Bug 1705369] Re: Ubuntu 17.10 boots to black screen when using Nvidia drivers (on a desktop with an Intel GPU)

2017-10-28 Thread Vadim Peretokin
See the steps we've already posted to alleviate the issue. Remove gdm

On Sat, 28 Oct 2017, 11:00 pm CaptSaltyJack, <1705...@bugs.launchpad.net>
wrote:

> Sorry to spam the comments, there's no edit feature. Once again I have a
> black screen with a blinking cursor, but I'm able to hit Ctrl+Alt+F6 to
> get to a shell. How do I troubleshoot this?
>
> --
> You received this bug notification because you are subscribed to a
> duplicate bug report (1726425).
> https://bugs.launchpad.net/bugs/1705369
>
> Title:
>   Ubuntu 17.10 boots to black screen when using Nvidia drivers (on a
>   desktop with an Intel GPU)
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1705369/+subscriptions
>

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1705369

Title:
  Ubuntu 17.10 boots to black screen when using Nvidia drivers (on a
  desktop with an Intel GPU)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1705369/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1502263] Re: Shutter does not work in Wayland

2017-10-28 Thread Vadim Peretokin
I don't see a clear solution that's not a workaround in that bug topic

On Sat, Oct 28, 2017 at 8:12 AM dino99 <1502...@bugs.launchpad.net>
wrote:

> ** Description changed:
>
>   Running Gnome 3.18 and Gnome Shell as the new Wayland Compositor,
>   shutter doesn't work. I.e. it's only creating a screenshot of the
>   shutter logo in a distorted way.
>
>   I don't if that's something that can be fixed easily, but it seems
>   Wayland (security) related.
>
>   Otherwise thanks for this outstanding screenshot tool!
>
>   Wolf
> + *
> + Main upstream discussion & fixes example to deal with wayland:
> + https://bugzilla.gnome.org/show_bug.cgi?id=776437
> + *
>
> --
> You received this bug notification because you are a member of Shutter
> Team, which is subscribed to shutter in Ubuntu.
> https://bugs.launchpad.net/bugs/1502263
>
> Title:
>   Shutter does not work in Wayland
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/shutter/+bug/1502263/+subscriptions
>


** Bug watch added: GNOME Bug Tracker #776437
   https://bugzilla.gnome.org/show_bug.cgi?id=776437

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1502263

Title:
  Shutter does not work in Wayland

To manage notifications about this bug go to:
https://bugs.launchpad.net/shutter/+bug/1502263/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1724564] Re: Cannot enter password to unlock encryption in 4.10

2017-10-27 Thread Vadim Peretokin
I did - the 4.10.0-38 kernel did the trick. Looks like it has been fixed
in the upcoming release?

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1724564

Title:
  Cannot enter password to unlock encryption in 4.10

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1724564/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Re: [Bug 1724564] Re: Cannot enter password to unlock encryption in 4.10

2017-10-26 Thread Vadim Peretokin
The first one couldn't install:

vadi@volga:~/Downloads$ ls
2410125510310.pdf  linux-headers-4.10.0-38-generic_4.10.0-38.42_amd64.deb
FML_FTE(1).pdf linux-image-4.10.0-38-generic_4.10.0-38.42_amd64.deb
FML_FTE.pdf
linux-image-extra-4.10.0-38-generic_4.10.0-38.42_amd64.deb
vadi@volga:~/Downloads$ sudo dpkg -i linux-*
[sudo] password for vadi:
Selecting previously unselected package linux-headers-4.10.0-38-generic.
(Reading database ... 397002 files and directories currently installed.)
Preparing to unpack linux-headers-4.10.0-38-generic_4.10.0-38.42_amd64.deb
...
Unpacking linux-headers-4.10.0-38-generic (4.10.0-38.42) ...
Selecting previously unselected package linux-image-4.10.0-38-generic.
Preparing to unpack linux-image-4.10.0-38-generic_4.10.0-38.42_amd64.deb ...
Examining /etc/kernel/preinst.d/
run-parts: executing /etc/kernel/preinst.d/intel-microcode
4.10.0-38-generic /boot/vmlinuz-4.10.0-38-generic
Done.
Unpacking linux-image-4.10.0-38-generic (4.10.0-38.42) ...
Selecting previously unselected package linux-image-extra-4.10.0-38-generic.
Preparing to unpack
linux-image-extra-4.10.0-38-generic_4.10.0-38.42_amd64.deb ...
Unpacking linux-image-extra-4.10.0-38-generic (4.10.0-38.42) ...
dpkg: dependency problems prevent configuration of
linux-headers-4.10.0-38-generic:
 linux-headers-4.10.0-38-generic depends on linux-headers-4.10.0-38;
however:
  Package linux-headers-4.10.0-38 is not installed.

dpkg: error processing package linux-headers-4.10.0-38-generic (--install):
 dependency problems - leaving unconfigured
Setting up linux-image-4.10.0-38-generic (4.10.0-38.42) ...
Running depmod.
update-initramfs: deferring update (hook will be called later)
Examining /etc/kernel/postinst.d.
run-parts: executing /etc/kernel/postinst.d/apt-auto-removal
4.10.0-38-generic /boot/vmlinuz-4.10.0-38-generic
run-parts: executing /etc/kernel/postinst.d/dkms 4.10.0-38-generic
/boot/vmlinuz-4.10.0-38-generic
ERROR (dkms apport): kernel package linux-headers-4.10.0-38-generic is not
supported
Error! Bad return status for module build on kernel: 4.10.0-38-generic
(x86_64)
Consult /var/lib/dkms/i915-4.11.6-4.10.0/1/build/make.log for more
information.
run-parts: executing /etc/kernel/postinst.d/initramfs-tools
4.10.0-38-generic /boot/vmlinuz-4.10.0-38-generic
update-initramfs: Generating /boot/initrd.img-4.10.0-38-generic
run-parts: executing /etc/kernel/postinst.d/pm-utils 4.10.0-38-generic
/boot/vmlinuz-4.10.0-38-generic
run-parts: executing /etc/kernel/postinst.d/unattended-upgrades
4.10.0-38-generic /boot/vmlinuz-4.10.0-38-generic
run-parts: executing /etc/kernel/postinst.d/update-notifier
4.10.0-38-generic /boot/vmlinuz-4.10.0-38-generic
run-parts: executing /etc/kernel/postinst.d/zz-update-grub
4.10.0-38-generic /boot/vmlinuz-4.10.0-38-generic
Generating grub configuration file ...
Found linux image: /boot/vmlinuz-4.14.0-041400rc6-generic
Found initrd image: /boot/initrd.img-4.14.0-041400rc6-generic
Found linux image: /boot/vmlinuz-4.10.0-38-generic
Found initrd image: /boot/initrd.img-4.10.0-38-generic
Found linux image: /boot/vmlinuz-4.10.0-37-generic
Found initrd image: /boot/initrd.img-4.10.0-37-generic
Found linux image: /boot/vmlinuz-4.10.0-35-generic
Found initrd image: /boot/initrd.img-4.10.0-35-generic
Found linux image: /boot/vmlinuz-4.9.45-040945-generic
Found initrd image: /boot/initrd.img-4.9.45-040945-generic
Adding boot menu entry for EFI firmware configuration
done
Setting up linux-image-extra-4.10.0-38-generic (4.10.0-38.42) ...
run-parts: executing /etc/kernel/postinst.d/apt-auto-removal
4.10.0-38-generic /boot/vmlinuz-4.10.0-38-generic
run-parts: executing /etc/kernel/postinst.d/dkms 4.10.0-38-generic
/boot/vmlinuz-4.10.0-38-generic
ERROR (dkms apport): kernel package linux-headers-4.10.0-38-generic is not
supported
Error! Bad return status for module build on kernel: 4.10.0-38-generic
(x86_64)
Consult /var/lib/dkms/i915-4.11.6-4.10.0/1/build/make.log for more
information.
run-parts: executing /etc/kernel/postinst.d/initramfs-tools
4.10.0-38-generic /boot/vmlinuz-4.10.0-38-generic
update-initramfs: Generating /boot/initrd.img-4.10.0-38-generic
run-parts: executing /etc/kernel/postinst.d/pm-utils 4.10.0-38-generic
/boot/vmlinuz-4.10.0-38-generic
run-parts: executing /etc/kernel/postinst.d/unattended-upgrades
4.10.0-38-generic /boot/vmlinuz-4.10.0-38-generic
run-parts: executing /etc/kernel/postinst.d/update-notifier
4.10.0-38-generic /boot/vmlinuz-4.10.0-38-generic
run-parts: executing /etc/kernel/postinst.d/zz-update-grub
4.10.0-38-generic /boot/vmlinuz-4.10.0-38-generic
Generating grub configuration file ...
Found linux image: /boot/vmlinuz-4.14.0-041400rc6-generic
Found initrd image: /boot/initrd.img-4.14.0-041400rc6-generic
Found linux image: /boot/vmlinuz-4.10.0-38-generic
Found initrd image: /boot/initrd.img-4.10.0-38-generic
Found linux image: /boot/vmlinuz-4.10.0-37-generic
Found initrd image: /boot/initrd.img-4.10.0-37-generic
Found linux image: /boot/vmlinuz-4.10.0-35-generic
Found ini

[Bug 1724564] Re: Cannot enter password to unlock encryption in 4.10

2017-10-25 Thread Vadim Peretokin
Ah, I see. Yes, v4.14-rc6 allows me to enter the disk password, however
wifi does not work: Ubuntu thinks the laptop has no wifi capability.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1724564

Title:
  Cannot enter password to unlock encryption in 4.10

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1724564/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1724564] Re: Cannot enter password to unlock encryption in 4.10

2017-10-24 Thread Vadim Peretokin
The mainline kernel is the only one I can actually use.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1724564

Title:
  Cannot enter password to unlock encryption in 4.10

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1724564/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1724564] Re: Cannot enter password to unlock encryption in 4.10

2017-10-24 Thread Vadim Peretokin
This issue is also preventing me from using paid snap applications (Hiri
for access to email for work) so it is rather urgent. Any other
information I can provide for this?

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1724564

Title:
  Cannot enter password to unlock encryption in 4.10

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1724564/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Re: [Bug 1705369] Re: Ubuntu 17.10 boots to black screen when using Nvidia drivers (on a desktop with an Intel GPU)

2017-10-24 Thread Vadim Peretokin
That did not work for me. I had to uninstall gdm3 completely in order to be
able to even get a login screen up.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1705369

Title:
  Ubuntu 17.10 boots to black screen when using Nvidia drivers (on a
  desktop with an Intel GPU)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1705369/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1726425] [NEW] gdm in Ubuntu 17.10 makes my system unbootable

2017-10-23 Thread Vadim Peretokin
Public bug reported:

With GDM installed, I cannot get to the Ubuntu login screen - it just
stays black until the monitor eventually shuts off.

The log has this helpful information about a "fail whale":

Oct 23 16:27:10 gooseberry dbus-daemon[3615]: Activating service 
name='org.gnome.ScreenSaver'
Oct 23 16:27:10 gooseberry gnome-screensav[3640]: Couldn't get presence status: 
The name org.gnome.SessionManager was not provided by any .service files
Oct 23 16:27:10 gooseberry dbus-daemon[3615]: Successfully activated service 
'org.gnome.ScreenSaver'
Oct 23 16:27:10 gooseberry gnome-session[3622]: gnome-session-binary[3622]: 
CRITICAL: We failed, but the fail whale is dead. Sorry
Oct 23 16:27:10 gooseberry gnome-session-binary[3622]: CRITICAL: We failed, but 
the fail whale is dead. Sorry
Oct 23 16:27:10 gooseberry gnome-screensav[3640]: gnome-screensaver: Fatal IO 
error 11 (Resource temporarily unavailable) on X server :0.
Oct 23 16:27:10 gooseberry org.a11y.atspi.Registry[3629]: XIO:  fatal IO error 
11 (Resource temporarily unavailable) on X server ":0"
Oct 23 16:27:10 gooseberry org.a11y.atspi.Registry[3629]:   after 21 
requests (21 known processed) with 0 events remaining.
Oct 23 16:27:10 gooseberry /usr/lib/gdm3/gdm-x-session[3587]: (II) evdev: 
Logitech USB Receiver: Close
Oct 23 16:27:10 gooseberry /usr/lib/gdm3/gdm-x-session[3587]: (II) 
UnloadModule: "evdev"
Oct 23 16:27:10 gooseberry /usr/lib/gdm3/gdm-x-session[3587]: (II) 
systemd-logind: releasing fd for 13:69
Oct 23 16:27:10 gooseberry /usr/lib/gdm3/gdm-x-session[3587]: (II) evdev: 
Logitech USB Receiver: Close
Oct 23 16:27:10 gooseberry /usr/lib/gdm3/gdm-x-session[3587]: (II) 
UnloadModule: "evdev"
Oct 23 16:27:10 gooseberry /usr/lib/gdm3/gdm-x-session[3587]: (II) 
systemd-logind: releasing fd for 13:68
Oct 23 16:27:10 gooseberry /usr/lib/gdm3/gdm-x-session[3587]: (II) evdev: 
Logitech USB Keyboard: Close
Oct 23 16:27:10 gooseberry /usr/lib/gdm3/gdm-x-session[3587]: (II) 
UnloadModule: "evdev"
Oct 23 16:27:10 gooseberry /usr/lib/gdm3/gdm-x-session[3587]: (II) 
systemd-logind: releasing fd for 13:67
Oct 23 16:27:10 gooseberry /usr/lib/gdm3/gdm-x-session[3587]: (II) evdev: 
Logitech USB Keyboard: Close
Oct 23 16:27:10 gooseberry /usr/lib/gdm3/gdm-x-session[3587]: (II) 
UnloadModule: "evdev"
Oct 23 16:27:10 gooseberry /usr/lib/gdm3/gdm-x-session[3587]: (II) 
systemd-logind: releasing fd for 13:66
Oct 23 16:27:10 gooseberry /usr/lib/gdm3/gdm-x-session[3587]: (II) evdev: Power 
Button: Close
Oct 23 16:27:10 gooseberry /usr/lib/gdm3/gdm-x-session[3587]: (II) 
UnloadModule: "evdev"
Oct 23 16:27:10 gooseberry /usr/lib/gdm3/gdm-x-session[3587]: (II) 
systemd-logind: releasing fd for 13:64
Oct 23 16:27:10 gooseberry /usr/lib/gdm3/gdm-x-session[3587]: (II) evdev: Power 
Button: Close
Oct 23 16:27:10 gooseberry /usr/lib/gdm3/gdm-x-session[3587]: (II) 
UnloadModule: "evdev"
Oct 23 16:27:10 gooseberry /usr/lib/gdm3/gdm-x-session[3587]: (II) 
systemd-logind: releasing fd for 13:65
Oct 23 16:27:10 gooseberry kernel: [   26.226446] nvidia-modeset: Freed GPU:0 
(GPU-d86402a0-4f53-8573-98c2-40295039d16c) @ PCI::01:00.0
Oct 23 16:27:10 gooseberry /usr/lib/gdm3/gdm-x-session[3587]: (II) 
NVIDIA(GPU-0): Deleting GPU-0
Oct 23 16:27:10 gooseberry /usr/lib/gdm3/gdm-x-session[3587]: (II) Server 
terminated successfully (0). Closing log file.
Oct 23 16:27:10 gooseberry systemd[1]: Stopping NVIDIA Persistence Daemon...
Oct 23 16:27:10 gooseberry nvidia-persistenced: Received signal 15
Oct 23 16:27:10 gooseberry nvidia-persistenced: Socket closed.

ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: gdm3 (not installed)
ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
Uname: Linux 4.13.0-16-generic x86_64
NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
ApportVersion: 2.20.7-0ubuntu3
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Mon Oct 23 16:31:33 2017
EcryptfsInUse: Yes
InstallationDate: Installed on 2012-03-23 (2039 days ago)
InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012)
SourcePackage: gdm3
UpgradeStatus: No upgrade log present (probably fresh install)
modified.conffile..etc.pam.d.gdm-password: [modified]
mtime.conffile..etc.pam.d.gdm-launch-environment: 2017-10-11T13:20:09
mtime.conffile..etc.pam.d.gdm-password: 2014-01-22T10:54:49

** Affects: gdm3 (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug artful

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1726425

Title:
  gdm in Ubuntu 17.10 makes my system unbootable

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1726425/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Re: [Bug 1725345] [NEW] Shutter doesn't work in Ubuntu 10.10 -- captures garbage screenshots

2017-10-23 Thread Vadim Peretokin
You need to switch to Xorg to use Shutter, Wayland is not supported. If
you'd like to do so, here is how: https://itsfoss.com/switch-xorg-wayland/

On Fri, Oct 20, 2017 at 5:50 PM Jonathan Kamens 
wrote:

> Public bug reported:
>
> The attached is what the image looks like when I tell shutter to capture
> a screenshot of my desktop.
>
> It looks similar when I try to capture by selection or by an individual
> window.
>
> Basically, all of the screenshots captured with shutter under 17.10
> using Wayland are garbage.
>
> Is there an alernative to shutter which we can use until such time as
> this is fixed?
>
> ProblemType: Bug
> DistroRelease: Ubuntu 17.10
> Package: shutter 0.93.1-2
> ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
> Uname: Linux 4.13.0-16-generic x86_64
> ApportVersion: 2.20.7-0ubuntu3
> Architecture: amd64
> CurrentDesktop: ubuntu:GNOME
> Date: Fri Oct 20 11:40:32 2017
> InstallationDate: Installed on 2017-05-19 (153 days ago)
> InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
> PackageArchitecture: all
> SourcePackage: shutter
> UpgradeStatus: Upgraded to artful on 2017-10-20 (0 days ago)
>
> ** Affects: shutter (Ubuntu)
>  Importance: Undecided
>  Status: New
>
>
> ** Tags: amd64 apport-bug artful wayland-session
>
> ** Attachment added: "Workspace 1_038.png"
>
> https://bugs.launchpad.net/bugs/1725345/+attachment/4979201/+files/Workspace%201_038.png
>
> --
> You received this bug notification because you are a member of Shutter
> Team, which is subscribed to shutter in Ubuntu.
> https://bugs.launchpad.net/bugs/1725345
>
> Title:
>   Shutter doesn't work in Ubuntu 10.10 -- captures garbage screenshots
>
> To manage notifications about this bug go to:
>
> https://bugs.launchpad.net/ubuntu/+source/shutter/+bug/1725345/+subscriptions
>

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1725345

Title:
  Shutter doesn't work in Ubuntu 10.10 -- captures garbage screenshots

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/shutter/+bug/1725345/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1726272] [NEW] Doesn't display any software

2017-10-23 Thread Vadim Peretokin
Public bug reported:

No software is loaded at all. I can't search for new software or view
existing software - the tool is a brick. See video for proof.

ProblemType: Bug
DistroRelease: Ubuntu 17.04
Package: ubuntu-software 3.22.7-0ubuntu3.17.04.5
Uname: Linux 4.9.45-040945-generic x86_64
ApportVersion: 2.20.4-0ubuntu4.5
Architecture: amd64
CurrentDesktop: Unity:Unity7
Date: Mon Oct 23 08:57:51 2017
EcryptfsInUse: Yes
InstallationDate: Installed on 2017-02-15 (249 days ago)
InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719)
PackageArchitecture: all
SourcePackage: gnome-software
UpgradeStatus: Upgraded to zesty on 2017-05-24 (151 days ago)

** Affects: gnome-software (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug third-party-packages zesty

** Attachment added: "Kazam_screencast_00022.mp4"
   
https://bugs.launchpad.net/bugs/1726272/+attachment/4987265/+files/Kazam_screencast_00022.mp4

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1726272

Title:
  Doesn't display any software

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1726272/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1726244] [NEW] Workrave applet does not work in Gnome Shell 17.10 under Xorg

2017-10-22 Thread Vadim Peretokin
Public bug reported:

The applet does not show up despite Workrave 1.10 advertising Gnome
Shell support:
http://www.workrave.org/blog/2013/01/13/workrave-110-released/

The current workaround is: https://askubuntu.com/questions/967264/how-
to-get-workrave-indicator-to-show-in-ubuntu-17-10/967425#967425

ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: workrave (not installed)
ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
Uname: Linux 4.13.0-16-generic x86_64
NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
ApportVersion: 2.20.7-0ubuntu3
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Mon Oct 23 07:12:19 2017
EcryptfsInUse: Yes
InstallationDate: Installed on 2012-03-23 (2039 days ago)
InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012)
SourcePackage: workrave
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: workrave (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug artful

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1726244

Title:
  Workrave applet does not work in Gnome Shell 17.10 under Xorg

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/workrave/+bug/1726244/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1725734] [NEW] Indicator size is too small

2017-10-21 Thread Vadim Peretokin
Public bug reported:

The indicator size in 17.10 is too small to be comfortable:

https://i.stack.imgur.com/r5Eza.png

ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: gnome-shell 3.26.1-0ubuntu4
ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
Uname: Linux 4.13.0-16-generic x86_64
NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
ApportVersion: 2.20.7-0ubuntu3
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Sat Oct 21 17:28:50 2017
DisplayManager: lightdm
EcryptfsInUse: Yes
InstallationDate: Installed on 2012-03-23 (2037 days ago)
InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012)
SourcePackage: gnome-shell
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: gnome-shell (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug artful

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1725734

Title:
  Indicator size is too small

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1725734/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1725641] [NEW] package network-manager-config-connectivity-ubuntu 1.8.4-1ubuntu3 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1

2017-10-21 Thread Vadim Peretokin
Public bug reported:

Botched upgrade from 17.04 to 17.10, the bug reporter came up after I
finally managed to login.

ProblemType: Package
DistroRelease: Ubuntu 17.10
Package: network-manager-config-connectivity-ubuntu 1.8.4-1ubuntu3
ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
Uname: Linux 4.13.0-16-generic x86_64
NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
ApportVersion: 2.20.7-0ubuntu3
AptOrdering:
 libdb5.3:amd64: Configure
 multiarch-support:amd64: Configure
 libobs0:amd64: Install
 obs-plugins:amd64: Install
 NULL: ConfigurePending
Architecture: amd64
Date: Sat Oct 21 10:13:28 2017
ErrorMessage: subprocess installed post-installation script returned error exit 
status 1
IfupdownConfig:
 auto lo
 iface lo inet loopback
InstallationDate: Installed on 2012-03-23 (2037 days ago)
InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012)
NetworkManager.state:
 [main]
 NetworkingEnabled=true
 WirelessEnabled=false
 WWANEnabled=true
PackageArchitecture: all
Python3Details: /usr/bin/python3.6, Python 3.6.3, python3-minimal, 
3.6.3-0ubuntu2
PythonDetails: /usr/bin/python2.7, Python 2.7.14, python-minimal, 
2.7.14-2ubuntu1
RelatedPackageVersions:
 dpkg 1.18.24ubuntu1
 apt  1.5
RfKill:
 0: phy0: Wireless LAN
Soft blocked: yes
Hard blocked: no
SourcePackage: network-manager
Title: package network-manager-config-connectivity-ubuntu 1.8.4-1ubuntu3 failed 
to install/upgrade: subprocess installed post-installation script returned 
error exit status 1
UpgradeStatus: No upgrade log present (probably fresh install)
nmcli-nm:
 RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  WIFI  
WWAN-HW  WWAN
 running  1.8.4connected  started  full  enabled enabled  
disabled  enabled  enabled

** Affects: network-manager (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-package artful

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1725641

Title:
  package network-manager-config-connectivity-ubuntu 1.8.4-1ubuntu3
  failed to install/upgrade: subprocess installed post-installation
  script returned error exit status 1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1725641/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1725640] [NEW] package obs-plugins 19.0.3+dfsg1-1 failed to install/upgrade: trying to overwrite '/usr/share/obs/obs-plugins/frontend-tools/locale/bn-BD.ini', which is also in package obs-studio

2017-10-21 Thread Vadim Peretokin
Public bug reported:

Botched upgrade from 17.04 to 17.10, the bug reporter came up after I
finally managed to login.

ProblemType: Package
DistroRelease: Ubuntu 17.10
Package: obs-plugins 19.0.3+dfsg1-1
ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
Uname: Linux 4.13.0-16-generic x86_64
NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
ApportVersion: 2.20.7-0ubuntu3
Architecture: amd64
Date: Sat Oct 21 10:01:19 2017
ErrorMessage: trying to overwrite 
'/usr/share/obs/obs-plugins/frontend-tools/locale/bn-BD.ini', which is also in 
package obs-studio 19.0.3-0obsproject1~xenial
InstallationDate: Installed on 2012-03-23 (2037 days ago)
InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012)
Python3Details: /usr/bin/python3.6, Python 3.6.3, python3-minimal, 
3.6.3-0ubuntu2
PythonDetails: /usr/bin/python2.7, Python 2.7.14, python-minimal, 
2.7.14-2ubuntu1
RelatedPackageVersions:
 dpkg 1.18.24ubuntu1
 apt  1.5
SourcePackage: obs-studio
Title: package obs-plugins 19.0.3+dfsg1-1 failed to install/upgrade: trying to 
overwrite '/usr/share/obs/obs-plugins/frontend-tools/locale/bn-BD.ini', which 
is also in package obs-studio 19.0.3-0obsproject1~xenial
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: obs-studio (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-package artful

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1725640

Title:
  package obs-plugins 19.0.3+dfsg1-1 failed to install/upgrade: trying
  to overwrite '/usr/share/obs/obs-plugins/frontend-tools/locale/bn-
  BD.ini', which is also in package obs-studio
  19.0.3-0obsproject1~xenial

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/obs-studio/+bug/1725640/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1725636] [NEW] package libobs0 19.0.3+dfsg1-1 failed to install/upgrade: trying to overwrite '/usr/share/obs/libobs/bicubic_scale.effect', which is also in package obs-studio 19.0.3-0obsproject1~

2017-10-21 Thread Vadim Peretokin
Public bug reported:

Botched upgrade from 17.04 to 17.10, the bug reporter came up after I
finally managed to login.

ProblemType: Package
DistroRelease: Ubuntu 17.10
Package: libobs0 19.0.3+dfsg1-1
ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
Uname: Linux 4.13.0-16-generic x86_64
NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
ApportVersion: 2.20.7-0ubuntu3
Architecture: amd64
Date: Sat Oct 21 10:00:19 2017
ErrorMessage: trying to overwrite '/usr/share/obs/libobs/bicubic_scale.effect', 
which is also in package obs-studio 19.0.3-0obsproject1~xenial
InstallationDate: Installed on 2012-03-23 (2037 days ago)
InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012)
Python3Details: /usr/bin/python3.6, Python 3.6.3, python3-minimal, 
3.6.3-0ubuntu2
PythonDetails: /usr/bin/python2.7, Python 2.7.14, python-minimal, 
2.7.14-2ubuntu1
RelatedPackageVersions:
 dpkg 1.18.24ubuntu1
 apt  1.5
SourcePackage: obs-studio
Title: package libobs0 19.0.3+dfsg1-1 failed to install/upgrade: trying to 
overwrite '/usr/share/obs/libobs/bicubic_scale.effect', which is also in 
package obs-studio 19.0.3-0obsproject1~xenial
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: obs-studio (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-package artful

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1725636

Title:
  package libobs0 19.0.3+dfsg1-1 failed to install/upgrade: trying to
  overwrite '/usr/share/obs/libobs/bicubic_scale.effect', which is also
  in package obs-studio 19.0.3-0obsproject1~xenial

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/obs-studio/+bug/1725636/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1725639] [NEW] package obs-plugins 19.0.3+dfsg1-1 failed to install/upgrade: trying to overwrite '/usr/share/obs/obs-plugins/frontend-tools/locale/bn-BD.ini', which is also in package obs-studio

2017-10-21 Thread Vadim Peretokin
Public bug reported:

Botched upgrade from 17.04 to 17.10, the bug reporter came up after I
finally managed to login.

ProblemType: Package
DistroRelease: Ubuntu 17.10
Package: obs-plugins 19.0.3+dfsg1-1
ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
Uname: Linux 4.13.0-16-generic x86_64
NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
ApportVersion: 2.20.7-0ubuntu3
Architecture: amd64
Date: Sat Oct 21 10:01:19 2017
ErrorMessage: trying to overwrite 
'/usr/share/obs/obs-plugins/frontend-tools/locale/bn-BD.ini', which is also in 
package obs-studio 19.0.3-0obsproject1~xenial
InstallationDate: Installed on 2012-03-23 (2037 days ago)
InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012)
Python3Details: /usr/bin/python3.6, Python 3.6.3, python3-minimal, 
3.6.3-0ubuntu2
PythonDetails: /usr/bin/python2.7, Python 2.7.14, python-minimal, 
2.7.14-2ubuntu1
RelatedPackageVersions:
 dpkg 1.18.24ubuntu1
 apt  1.5
SourcePackage: obs-studio
Title: package obs-plugins 19.0.3+dfsg1-1 failed to install/upgrade: trying to 
overwrite '/usr/share/obs/obs-plugins/frontend-tools/locale/bn-BD.ini', which 
is also in package obs-studio 19.0.3-0obsproject1~xenial
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: obs-studio (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-package artful

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1725639

Title:
  package obs-plugins 19.0.3+dfsg1-1 failed to install/upgrade: trying
  to overwrite '/usr/share/obs/obs-plugins/frontend-tools/locale/bn-
  BD.ini', which is also in package obs-studio
  19.0.3-0obsproject1~xenial

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/obs-studio/+bug/1725639/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1724564] Re: Cannot enter password to unlock encryption in 4.10

2017-10-20 Thread Vadim Peretokin
It's a bit of a problem since this is blocking me from upgrading to
Ubuntu 17.10.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1724564

Title:
  Cannot enter password to unlock encryption in 4.10

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1724564/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1720092] Re: Won't connect to wifi unless power_save is disabled

2017-10-20 Thread Vadim Peretokin
The issue still persists on a mainline kernel.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1720092

Title:
  Won't connect to wifi unless power_save is disabled

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1720092/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1724564] Re: Cannot enter password to unlock encryption in 4.10

2017-10-19 Thread Vadim Peretokin
apport information

** Tags added: apport-collected zesty

** Description changed:

- I'm unable to enter my password on the screen to unlock the disk during
- boot using kernels 4.10.0-35 and 4.10.0-37. Using the 4.9.45-040945
- mainline kernel seems to work fine.
+ I'm unable to enter my password on the screen to unlock the disk during boot 
using kernels 4.10.0-35 and 4.10.0-37. Using the 4.9.45-040945 mainline kernel 
seems to work fine.
+ --- 
+ ApportVersion: 2.20.4-0ubuntu4.5
+ Architecture: amd64
+ CurrentDesktop: Unity:Unity7
+ DistroRelease: Ubuntu 17.04
+ EcryptfsInUse: Yes
+ InstallationDate: Installed on 2017-02-15 (245 days ago)
+ InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
+ Package: linux (not installed)
+ Tags:  zesty
+ Uname: Linux 4.9.45-040945-generic x86_64
+ UnreportableReason: The running kernel is not an Ubuntu kernel
+ UpgradeStatus: Upgraded to zesty on 2017-05-24 (147 days ago)
+ UserGroups: adm cdrom dip docker lpadmin plugdev sambashare sudo wireshark
+ _MarkForUpload: True

** Attachment added: "JournalErrors.txt"
   
https://bugs.launchpad.net/bugs/1724564/+attachment/4975626/+files/JournalErrors.txt

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1724564

Title:
  Cannot enter password to unlock encryption in 4.10

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1724564/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1724564] ProcEnviron.txt

2017-10-19 Thread Vadim Peretokin
apport information

** Attachment added: "ProcEnviron.txt"
   
https://bugs.launchpad.net/bugs/1724564/+attachment/4975628/+files/ProcEnviron.txt

** Changed in: linux (Ubuntu)
   Status: Incomplete => Confirmed

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1724564

Title:
  Cannot enter password to unlock encryption in 4.10

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1724564/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1724564] ProcCpuinfoMinimal.txt

2017-10-19 Thread Vadim Peretokin
apport information

** Attachment added: "ProcCpuinfoMinimal.txt"
   
https://bugs.launchpad.net/bugs/1724564/+attachment/4975627/+files/ProcCpuinfoMinimal.txt

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1724564

Title:
  Cannot enter password to unlock encryption in 4.10

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1724564/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1724564] [NEW] Cannot enter password to unlock encryption in 4.10

2017-10-18 Thread Vadim Peretokin
Public bug reported:

I'm unable to enter my password on the screen to unlock the disk during
boot using kernels 4.10.0-35 and 4.10.0-37. Using the 4.9.45-040945
mainline kernel seems to work fine.

** Affects: linux (Ubuntu)
 Importance: Undecided
 Status: New

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1724564

Title:
  Cannot enter password to unlock encryption in 4.10

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1724564/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Re: [Bug 1502263] Re: Shutter does not work in Wayland

2017-10-13 Thread Vadim Peretokin
Can it edit and upload screenshots?

On Fri, Oct 13, 2017 at 1:39 PM André <1502...@bugs.launchpad.net>
wrote:

> gnome-screenshot works
>
> --
> You received this bug notification because you are a member of Shutter
> Team, which is subscribed to shutter in Ubuntu.
> https://bugs.launchpad.net/bugs/1502263
>
> Title:
>   Shutter does not work in Wayland
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/shutter/+bug/1502263/+subscriptions
>

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1502263

Title:
  Shutter does not work in Wayland

To manage notifications about this bug go to:
https://bugs.launchpad.net/shutter/+bug/1502263/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Re: [Bug 1720092] Re: Won't connect to wifi unless power_save is disabled

2017-09-29 Thread Vadim Peretokin
"First, if one is using select proprietary or out-of-tree modules (ex.
vitualbox, nvidia, fglrx, bcmwl, etc.) unless there is an *extra* package
available for the version you are testing, you will need to uninstall the
module first, in order to test the mainline kernel."

I'm using Virtualbox, but the instructions don't say how to uninstall a
module.

On Thu, Sep 28, 2017 at 4:31 PM Joseph Salisbury <
joseph.salisb...@canonical.com> wrote:

> Did this issue start happening after an update/upgrade?  Was there a
> prior kernel version where you were not having this particular problem?
>
> Would it be possible for you to test the latest upstream kernel? Refer
> to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest
> v4.14 kernel[0].
>
> If this bug is fixed in the mainline kernel, please add the following
> tag 'kernel-fixed-upstream'.
>
> If the mainline kernel does not fix this bug, please add the tag:
> 'kernel-bug-exists-upstream'.
>
> Once testing of the upstream kernel is complete, please mark this bug as
> "Confirmed".
>
>
> Thanks in advance.
>
> [0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.14-rc2/
>
> ** Changed in: linux (Ubuntu)
>Importance: Undecided => Medium
>
> ** Changed in: linux (Ubuntu)
>Status: Confirmed => Incomplete
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1720092
>
> Title:
>   Won't connect to wifi unless power_save is disabled
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1720092/+subscriptions
>

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1720092

Title:
  Won't connect to wifi unless power_save is disabled

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1720092/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1720092] [NEW] Won't connect to wifi unless power_save is disabled

2017-09-28 Thread Vadim Peretokin
Public bug reported:

I can connect to most WiFi networks fine, however for one particular
WPA/WPA2, EAP-PEAP, MSCHAPV2 network I have to do "sudo iw wlp1s0 set
power_save off" before it is able to connect.

ProblemType: Bug
DistroRelease: Ubuntu 17.04
Package: linux-image-4.10.0-35-generic 4.10.0-35.39
ProcVersionSignature: Ubuntu 4.10.0-35.39-generic 4.10.17
Uname: Linux 4.10.0-35-generic x86_64
ApportVersion: 2.20.4-0ubuntu4.5
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/pcmC0D0c:   vadi   4472 F...m pulseaudio
 /dev/snd/pcmC0D0p:   vadi   4472 F...m pulseaudio
 /dev/snd/controlC0:  vadi   4472 F pulseaudio
CurrentDesktop: Unity:Unity7
Date: Thu Sep 28 10:09:15 2017
EcryptfsInUse: Yes
HibernationDevice: RESUME=UUID=8c0e25d4-6e36-428e-b354-4c71b99db752
InstallationDate: Installed on 2017-02-15 (224 days ago)
InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719)
Lsusb:
 Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
 Bus 001 Device 003: ID 0a5c:5805 Broadcom Corp. 
 Bus 001 Device 002: ID 0bda:5686 Realtek Semiconductor Corp. 
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: Dell Inc. Latitude E7470
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.10.0-35-generic.efi.signed 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
RelatedPackageVersions:
 linux-restricted-modules-4.10.0-35-generic N/A
 linux-backports-modules-4.10.0-35-generic  N/A
 linux-firmware 1.164.1
SourcePackage: linux
UpgradeStatus: Upgraded to zesty on 2017-05-24 (126 days ago)
dmi.bios.date: 06/02/2017
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 1.16.4
dmi.board.name: 0T6HHJ
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 9
dmi.chassis.vendor: Dell Inc.
dmi.modalias: 
dmi:bvnDellInc.:bvr1.16.4:bd06/02/2017:svnDellInc.:pnLatitudeE7470:pvr:rvnDellInc.:rn0T6HHJ:rvrA00:cvnDellInc.:ct9:cvr:
dmi.product.name: Latitude E7470
dmi.sys.vendor: Dell Inc.

** Affects: linux (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug zesty

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1720092

Title:
  Won't connect to wifi unless power_save is disabled

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1720092/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1310680] Re: Links don't work

2017-09-03 Thread Vadim Peretokin
I've got Firefox installed, but Synaptic fails at using it correctly -
Firefox says "Your Firefox profile cannot be loaded. It may be missing
or inaccessible." when I click on the homepage link.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1310680

Title:
  Links don't work

To manage notifications about this bug go to:
https://bugs.launchpad.net/synaptic/+bug/1310680/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 1712862] [NEW] VPN auto-connection does not work at login

2017-08-24 Thread Vadim Peretokin
Public bug reported:

I've setup the VPN to autoconnect on login. When I log in, the
connection keeps failing to establish. If I disconnect from the network
it's trying to connect to and click connect manually, it is able to
connect to the network and the VPN straight away.

Essentially, every time I log in I have to manually disconnect and
reconnect to a network - and the autoconnecting bit fails to do its job.

ProblemType: Bug
DistroRelease: Ubuntu 17.04
Package: network-manager 1.4.4-1ubuntu3.1
ProcVersionSignature: Ubuntu 4.10.0-32.36-generic 4.10.17
Uname: Linux 4.10.0-32-generic x86_64
NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
ApportVersion: 2.20.4-0ubuntu4.5
Architecture: amd64
CurrentDesktop: Unity:Unity7
Date: Thu Aug 24 18:01:01 2017
EcryptfsInUse: Yes
IfupdownConfig:
 auto lo
 iface lo inet loopback
InstallationDate: Installed on 2012-03-23 (1979 days ago)
InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012)
NetworkManager.conf:
 [main]
 plugins=ifupdown,keyfile
 
 [ifupdown]
 managed=false
NetworkManager.state:
 [main]
 NetworkingEnabled=true
 WirelessEnabled=true
 WWANEnabled=true
RfKill:
 0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
SourcePackage: network-manager
UpgradeStatus: Upgraded to zesty on 2017-06-24 (61 days ago)
nmcli-nm:
 RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  WIFI  
   WWAN-HW  WWAN
 running  1.4.4connected  started  full  enabled enabled  
enabled  enabled  enabled

** Affects: network-manager (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug zesty

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1712862

Title:
  VPN auto-connection does not work at login

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1712862/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 1633319] Re: memory leak in indicator-datetime

2017-06-07 Thread Vadim Peretokin
I had to disable Evolution accessing the calendar in Online Accounts,
because the whole OS was completely unusable - as soon as I logged in,
indicator-datetime-service would eat up all of the memory and lock the
system up. That's it.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1633319

Title:
  memory leak in indicator-datetime

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/indicator-datetime/+bug/1633319/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 1695573] [NEW] Crashes after installing

2017-06-02 Thread Vadim Peretokin
Public bug reported:

sudo system-config-samba

(system-config-samba:10277): IBUS-WARNING **: The owner of 
/home/vadi/.config/ibus/bus is not root!
Traceback (most recent call last):
  File "/usr/sbin/system-config-samba", line 45, in 
mainWindow.MainWindow(debug_flag)
  File "/usr/share/system-config-samba/mainWindow.py", line 121, in __init__
self.basic_preferences_win = basicPreferencesWin.BasicPreferencesWin(self, 
self.xml, self.samba_data, self.samba_backend, self.main_window)
  File "/usr/share/system-config-samba/basicPreferencesWin.py", line 97, in 
__init__
self.admin = libuser.admin()
SystemError: could not open configuration file `/etc/libuser.conf': No such 
file or directory

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: system-config-samba 1.2.63-0ubuntu6
ProcVersionSignature: Ubuntu 4.4.0-78.99-generic 4.4.62
Uname: Linux 4.4.0-78-generic x86_64
NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
ApportVersion: 2.20.1-0ubuntu2.6
Architecture: amd64
CurrentDesktop: Unity
Date: Sat Jun  3 05:50:53 2017
EcryptfsInUse: Yes
InstallationDate: Installed on 2012-03-23 (1897 days ago)
InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012)
PackageArchitecture: all
SourcePackage: system-config-samba
UpgradeStatus: Upgraded to xenial on 2016-07-29 (309 days ago)

** Affects: system-config-samba (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug xenial

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1695573

Title:
  Crashes after installing

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/system-config-samba/+bug/1695573/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 1693172] Re: package phpmyadmin 4:4.6.4+dfsg1-1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 2

2017-05-24 Thread Vadim Peretokin
Might be a duplicate of #1641302.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1693172

Title:
  package phpmyadmin 4:4.6.4+dfsg1-1 failed to install/upgrade:
  subprocess installed post-installation script returned error exit
  status 2

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/phpmyadmin/+bug/1693172/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 1693172] [NEW] package phpmyadmin 4:4.6.4+dfsg1-1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 2

2017-05-24 Thread Vadim Peretokin
Public bug reported:

Got the issue while upgrading to Ubuntu 16.10 from 16.04.

ProblemType: Package
DistroRelease: Ubuntu 16.10
Package: phpmyadmin 4:4.6.4+dfsg1-1
ProcVersionSignature: Ubuntu 4.8.0-52.55~16.04.1-generic 4.8.17
Uname: Linux 4.8.0-52-generic x86_64
ApportVersion: 2.20.3-0ubuntu8.3
Architecture: amd64
Date: Wed May 24 12:54:35 2017
ErrorMessage: subprocess installed post-installation script returned error exit 
status 2
InstallationDate: Installed on 2017-02-15 (98 days ago)
InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719)
PackageArchitecture: all
RelatedPackageVersions:
 dpkg 1.18.10ubuntu1.1
 apt  1.3.5
SourcePackage: phpmyadmin
Title: package phpmyadmin 4:4.6.4+dfsg1-1 failed to install/upgrade: subprocess 
installed post-installation script returned error exit status 2
UpgradeStatus: Upgraded to yakkety on 2017-05-24 (0 days ago)

** Affects: phpmyadmin (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-package yakkety

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1693172

Title:
  package phpmyadmin 4:4.6.4+dfsg1-1 failed to install/upgrade:
  subprocess installed post-installation script returned error exit
  status 2

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/phpmyadmin/+bug/1693172/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 1678368] Re: /usr/games/mudlet:11:std::_Deque_iterator:std::_Deque_iterator:std::_Deque_iterator:std::deque:TTextEdit::highlight

2017-03-31 Thread Vadim Peretokin
Only happens on 2.1, no reports on 3.0.

** Changed in: mudlet (Ubuntu)
   Status: New => Invalid

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1678368

Title:
  
/usr/games/mudlet:11:std::_Deque_iterator:std::_Deque_iterator:std::_Deque_iterator:std::deque:TTextEdit::highlight

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mudlet/+bug/1678368/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 1670586] Re: /usr/games/mudlet:11:QExplicitlySharedDataPointer:QNetworkConfiguration::~QNetworkConfiguration:QHashData::free_helper:QHash:QHash

2017-03-31 Thread Vadim Peretokin
Migrating issues to Github, please follow the new discussion here:
https://github.com/Mudlet/Mudlet/issues/588

This issue needs to be closed and there is no appropriate status, so
will set it to "Opinion" just for migration purposes.

** Bug watch added: github.com/Mudlet/Mudlet/issues #588
   https://github.com/Mudlet/Mudlet/issues/588

** Changed in: mudlet
   Status: Incomplete => Opinion

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1670586

Title:
  
/usr/games/mudlet:11:QExplicitlySharedDataPointer:QNetworkConfiguration::~QNetworkConfiguration:QHashData::free_helper:QHash:QHash

To manage notifications about this bug go to:
https://bugs.launchpad.net/mudlet/+bug/1670586/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


Re: [Mudlet-makers] [Bug 1670586] Re: /usr/games/mudlet:11:QExplicitlySharedDataPointer:QNetworkConfiguration::~QNetworkConfiguration:QHashData::free_helper:QHash:QHash

2017-03-15 Thread Vadim Peretokin
I found it. Why do you disagree with it? See top - "Users of the Ubuntu
operating system have entrusted Canonical (“us” and “we”) with the data
submitted in error reports.". This is data for all Ubuntu users who submit
bug reports. When I submit my bug report and submit potentially personally
identifyable information, I would not want any random person off the web to
download it and hand it out to anyone else... it makes sense to me.

It's not a hinderance to us to look at it, it's just that we should not be
giving our private information to anyone else?

On Wed, Mar 15, 2017 at 6:08 PM Vadim Peretokin 
wrote:

> Where is this text?
>
> On Wed, Mar 15, 2017 at 5:17 PM Stephen Lyons 
> wrote:
>
> Tried to look at the errors.ubuntu.com site but found I do have access
> and have to sign up and agree to terms such as:
>
> > ...
> > (ii) you agree that you will not:
> >
> >batch download the data for off-line processing;
> >
> >disclose or share the data with any third party, without Canonical's
> express written consent; and...
>
> Given that last line - that I cannot discuss anything I might find in
> the bug report with anyone else without having "permission" in writing
> make me think "sod it" - if they don't want to tell us more about the
> issue they are having then I will resist (hard as it might be!) the urge
> to rush off and try and fix it - if others are having an issue I trust
> they would be a little more willing to openly tell what is wrong...
>
> ** Changed in: mudlet
>Importance: Undecided => Low
>
> ** Changed in: mudlet
>Status: New => Incomplete
>
> ** Changed in: mudlet (Ubuntu)
>Status: New => Incomplete
>
> --
> You received this bug notification because you are a member of Mudlet
> Makers, which is subscribed to Mudlet.
> https://bugs.launchpad.net/bugs/1670586
>
> Title:
>
> /usr/games/mudlet:11:QExplicitlySharedDataPointer:QNetworkConfiguration::~QNetworkConfiguration:QHashData::free_helper:QHash:QHash
>
> Status in Mudlet:
>   Incomplete
> Status in mudlet package in Ubuntu:
>   Incomplete
>
> Bug description:
>   The Ubuntu Error Tracker has been receiving reports about a problem
> regarding mudlet.  This problem was most recently seen with package version
> 1:3.0.0~delta-3, the problem page at
> https://errors.ubuntu.com/problem/59f70700f1cb39d4a932f21b51ef5172da315be4
> contains more details, including versions of packages affected, stacktrace
> or traceback, and individual crash reports.
>   If you do not have access to the Ubuntu Error Tracker you can request it
> at http://forms.canonical.com/reports/.
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/mudlet/+bug/1670586/+subscriptions
>
> ___
> Mailing list: https://launchpad.net/~mudlet-makers
> Post to : mudlet-mak...@lists.launchpad.net
> Unsubscribe : https://launchpad.net/~mudlet-makers
> More help   : https://help.launchpad.net/ListHelp
>
>

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1670586

Title:
  
/usr/games/mudlet:11:QExplicitlySharedDataPointer:QNetworkConfiguration::~QNetworkConfiguration:QHashData::free_helper:QHash:QHash

To manage notifications about this bug go to:
https://bugs.launchpad.net/mudlet/+bug/1670586/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Re: [Mudlet-makers] [Bug 1670586] Re: /usr/games/mudlet:11:QExplicitlySharedDataPointer:QNetworkConfiguration::~QNetworkConfiguration:QHashData::free_helper:QHash:QHash

2017-03-15 Thread Vadim Peretokin
Where is this text?

On Wed, Mar 15, 2017 at 5:17 PM Stephen Lyons 
wrote:

> Tried to look at the errors.ubuntu.com site but found I do have access
> and have to sign up and agree to terms such as:
>
> > ...
> > (ii) you agree that you will not:
> >
> >batch download the data for off-line processing;
> >
> >disclose or share the data with any third party, without Canonical's
> express written consent; and...
>
> Given that last line - that I cannot discuss anything I might find in
> the bug report with anyone else without having "permission" in writing
> make me think "sod it" - if they don't want to tell us more about the
> issue they are having then I will resist (hard as it might be!) the urge
> to rush off and try and fix it - if others are having an issue I trust
> they would be a little more willing to openly tell what is wrong...
>
> ** Changed in: mudlet
>Importance: Undecided => Low
>
> ** Changed in: mudlet
>Status: New => Incomplete
>
> ** Changed in: mudlet (Ubuntu)
>Status: New => Incomplete
>
> --
> You received this bug notification because you are a member of Mudlet
> Makers, which is subscribed to Mudlet.
> https://bugs.launchpad.net/bugs/1670586
>
> Title:
>
> /usr/games/mudlet:11:QExplicitlySharedDataPointer:QNetworkConfiguration::~QNetworkConfiguration:QHashData::free_helper:QHash:QHash
>
> Status in Mudlet:
>   Incomplete
> Status in mudlet package in Ubuntu:
>   Incomplete
>
> Bug description:
>   The Ubuntu Error Tracker has been receiving reports about a problem
> regarding mudlet.  This problem was most recently seen with package version
> 1:3.0.0~delta-3, the problem page at
> https://errors.ubuntu.com/problem/59f70700f1cb39d4a932f21b51ef5172da315be4
> contains more details, including versions of packages affected, stacktrace
> or traceback, and individual crash reports.
>   If you do not have access to the Ubuntu Error Tracker you can request it
> at http://forms.canonical.com/reports/.
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/mudlet/+bug/1670586/+subscriptions
>
> ___
> Mailing list: https://launchpad.net/~mudlet-makers
> Post to : mudlet-mak...@lists.launchpad.net
> Unsubscribe : https://launchpad.net/~mudlet-makers
> More help   : https://help.launchpad.net/ListHelp
>

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1670586

Title:
  
/usr/games/mudlet:11:QExplicitlySharedDataPointer:QNetworkConfiguration::~QNetworkConfiguration:QHashData::free_helper:QHash:QHash

To manage notifications about this bug go to:
https://bugs.launchpad.net/mudlet/+bug/1670586/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 1670586] Re: /usr/games/mudlet:11:QExplicitlySharedDataPointer:QNetworkConfiguration::~QNetworkConfiguration:QHashData::free_helper:QHash:QHash

2017-03-14 Thread Vadim Peretokin
** Also affects: mudlet
   Importance: Undecided
   Status: New

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1670586

Title:
  
/usr/games/mudlet:11:QExplicitlySharedDataPointer:QNetworkConfiguration::~QNetworkConfiguration:QHashData::free_helper:QHash:QHash

To manage notifications about this bug go to:
https://bugs.launchpad.net/mudlet/+bug/1670586/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 1375978] Re: Crash in postMessage

2017-03-06 Thread Vadim Peretokin
Marking it as fixed released because this error has only been happening
with 2.1 and not at all with any of the later versions.

** Changed in: mudlet (Ubuntu)
   Status: New => Fix Released

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1375978

Title:
  Crash in postMessage

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mudlet/+bug/1375978/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 1670586] Re: /usr/games/mudlet:11:QExplicitlySharedDataPointer:QNetworkConfiguration::~QNetworkConfiguration:QHashData::free_helper:QHash:QHash

2017-03-06 Thread Vadim Peretokin
There is also
https://errors.ubuntu.com/problem/64b26f34800c2bdb8d224445864300815631c7de
which has a very similar signature:

mudlet (11) QExplicitlySharedDataPointer → QNetworkConfiguration → →
~QNetworkConfiguration → QHashNode → QHash → QHashData → → free_helper

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1670586

Title:
  
/usr/games/mudlet:11:QExplicitlySharedDataPointer:QNetworkConfiguration::~QNetworkConfiguration:QHashData::free_helper:QHash:QHash

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mudlet/+bug/1670586/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1670586] Re: /usr/games/mudlet:11:QExplicitlySharedDataPointer:QNetworkConfiguration::~QNetworkConfiguration:QHashData::free_helper:QHash:QHash

2017-03-06 Thread Vadim Peretokin
I made this bug report from the Ubuntu error tracker - it's a bug in
3.0.0~delta as it mentions on that page and people have been crashing a
fair bit with it. That's just with Ubuntu, arguably one of our smallest
userbases...

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1670586

Title:
  
/usr/games/mudlet:11:QExplicitlySharedDataPointer:QNetworkConfiguration::~QNetworkConfiguration:QHashData::free_helper:QHash:QHash

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mudlet/+bug/1670586/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 1572569] Re: Relocation error in libc.so.6

2017-02-12 Thread Vadim Peretokin
Is that a serious suggestion though? Because in order to get your
software deployed on older versions of Ubuntu, you must compile on the
older version of the OS, not on a newer one. This is catch-22 advice
right here.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1572569

Title:
  Relocation error in libc.so.6

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/glibc/+bug/1572569/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 1547232] [NEW] Unity got stuck moving a window in Workspaces view

2016-02-18 Thread Vadim Peretokin
Public bug reported:

Somehow Unity got stuck moving a window, and there was nothing I could
do but log off.

ProblemType: Bug
DistroRelease: Ubuntu 15.10
Package: unity 7.3.3+15.10.20151203-0ubuntu1
ProcVersionSignature: Ubuntu 4.2.0-27.32-generic 4.2.8-ckt1
Uname: Linux 4.2.0-27-generic x86_64
NonfreeKernelModules: fglrx
.tmp.unity.support.test.0:
 
ApportVersion: 2.19.1-0ubuntu5
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: Fri Feb 19 07:50:54 2016
DistUpgraded: 2015-10-27 08:48:20,176 DEBUG enabling apt cron job
DistroCodename: wily
DistroVariant: ubuntu
DkmsStatus:
 fglrx-updates-core, 15.201, 4.2.0-23-generic, x86_64: installed
 fglrx-updates-core, 15.201, 4.2.0-25-generic, x86_64: installed
 fglrx-updates-core, 15.201, 4.2.0-27-generic, x86_64: installed
 vboxhost, 5.0.14, 4.2.0-25-generic, x86_64: installed
 vboxhost, 5.0.14, 4.2.0-27-generic, x86_64: installed
GraphicsCard:
 Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] (rev 
0b) (prog-if 00 [VGA controller])
   Subsystem: Hewlett-Packard Company Device [103c:198f]
 Advanced Micro Devices, Inc. [AMD/ATI] Mars [Radeon HD 8730M] [1002:6601] 
(prog-if 00 [VGA controller])
   Subsystem: Hewlett-Packard Company FirePro M4100 [103c:2100]
InstallationDate: Installed on 2014-06-26 (601 days ago)
InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
MachineType: Hewlett-Packard HP ZBook 14
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.2.0-27-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash
SourcePackage: unity
UpgradeStatus: Upgraded to wily on 2015-10-26 (114 days ago)
dmi.bios.date: 04/29/2014
dmi.bios.vendor: Hewlett-Packard
dmi.bios.version: L71 Ver. 01.11
dmi.board.name: 198F
dmi.board.vendor: Hewlett-Packard
dmi.board.version: KBC Version 15.54
dmi.chassis.asset.tag: CNU424B3ZZ
dmi.chassis.type: 10
dmi.chassis.vendor: Hewlett-Packard
dmi.modalias: 
dmi:bvnHewlett-Packard:bvrL71Ver.01.11:bd04/29/2014:svnHewlett-Packard:pnHPZBook14:pvrA3009DD10303:rvnHewlett-Packard:rn198F:rvrKBCVersion15.54:cvnHewlett-Packard:ct10:cvr:
dmi.product.name: HP ZBook 14
dmi.product.version: A3009DD10303
dmi.sys.vendor: Hewlett-Packard
version.compiz: compiz 1:0.9.12.2+15.10.20151202-0ubuntu1
version.fglrx-installer: fglrx-installer N/A
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.64-1
version.libgl1-mesa-dri: libgl1-mesa-dri 11.0.2-1ubuntu4
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 11.0.2-1ubuntu4
version.xserver-xorg-core: xserver-xorg-core 2:1.17.2-1ubuntu9.1
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.2-1ubuntu1
version.xserver-xorg-video-ati: xserver-xorg-video-ati 
1:7.5.0+git20150819-0ubuntu1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20150808-0ubuntu4
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.11-1ubuntu3
xserver.bootTime: Fri Feb 19 07:49:48 2016
xserver.configfile: default
xserver.errors:
 
xserver.logfile: /var/log/Xorg.0.log
xserver.outputs:
 product id4925 
 vendor AUO
xserver.version: 2:1.17.2-1ubuntu9.1

** Affects: unity (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug compiz-0.9 ubuntu wily

** Attachment added: "Screenshot from 2016-02-19 07-38-45.png"
   
https://bugs.launchpad.net/bugs/1547232/+attachment/4575000/+files/Screenshot%20from%202016-02-19%2007-38-45.png

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1547232

Title:
  Unity got stuck moving a window in Workspaces view

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1547232/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 1539634] Re: network-manager crashes when using libnl-3-200-3.21.1-1ubuntu1

2016-01-30 Thread Vadim Peretokin
Yep, already have ran into that problem - rebooted and had no internet
due to NM repeatedly crashing. This is a severe issue.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1539634

Title:
  network-manager crashes when using libnl-3-200-3.21.1-1ubuntu1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1539634/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 1540014] [NEW] NetworkManager crashes over and over again, and does not launch

2016-01-30 Thread Vadim Peretokin
Public bug reported:

I did the kernel updates this morning, restarted my computer, and had no
internet. Tried using an older kernel version, manually starting
NetworkManager, all the things - nothing works, there is no internet.

All NetworkManager is doing is crashing repeatedly and that's about it:

Jan 31 09:38:07 gooseberry ModemManager[3692]:   ModemManager (version 
1.0.0) starting...
Jan 31 09:38:07 gooseberry NetworkManager[3699]:  NetworkManager (version 
0.9.8.8) is starting...
Jan 31 09:38:07 gooseberry NetworkManager[3699]:  Read config file 
/etc/NetworkManager/NetworkManager.conf
Jan 31 09:38:07 gooseberry NetworkManager[3699]:  WEXT support is enabled
Jan 31 09:38:07 gooseberry kernel: [  161.385758] do_general_protection: 1 
callbacks suppressed
Jan 31 09:38:07 gooseberry kernel: [  161.385761] traps: NetworkManager[3699] 
general protection ip:469fee sp:7ffc1d7ddfc0 error:0 in 
NetworkManager[40+10d000]
Jan 31 09:38:07 gooseberry kernel: [  161.460737] init: network-manager main 
process (3699) killed by SEGV signal
Jan 31 09:38:07 gooseberry kernel: [  161.460749] init: network-manager main 
process ended, respawning
Jan 31 09:38:07 gooseberry NetworkManager[3707]:  NetworkManager (version 
0.9.8.8) is starting...
Jan 31 09:38:07 gooseberry NetworkManager[3707]:  Read config file 
/etc/NetworkManager/NetworkManager.conf
Jan 31 09:38:07 gooseberry NetworkManager[3707]:  WEXT support is enabled
Jan 31 09:38:07 gooseberry kernel: [  161.469470] traps: NetworkManager[3707] 
general protection ip:469fee sp:7ffdedbe8250 error:0 in 
NetworkManager[40+10d000]
Jan 31 09:38:07 gooseberry kernel: [  161.543303] init: network-manager main 
process (3707) killed by SEGV signal
Jan 31 09:38:07 gooseberry kernel: [  161.543324] init: network-manager main 
process ended, respawning
Jan 31 09:38:07 gooseberry NetworkManager[3712]:  NetworkManager (version 
0.9.8.8) is starting...
Jan 31 09:38:07 gooseberry NetworkManager[3712]:  Read config file 
/etc/NetworkManager/NetworkManager.conf
Jan 31 09:38:07 gooseberry NetworkManager[3712]:  WEXT support is enabled
Jan 31 09:38:07 gooseberry kernel: [  161.549176] traps: NetworkManager[3712] 
general protection ip:469fee sp:7fff0dc74c20 error:0 in 
NetworkManager[40+10d000]
Jan 31 09:38:07 gooseberry kernel: [  161.626148] init: network-manager main 
process (3712) killed by SEGV signal
Jan 31 09:38:07 gooseberry kernel: [  161.626169] init: network-manager main 
process ended, respawning
Jan 31 09:38:07 gooseberry NetworkManager[3717]:  NetworkManager (version 
0.9.8.8) is starting...
Jan 31 09:38:07 gooseberry NetworkManager[3717]:  Read config file 
/etc/NetworkManager/NetworkManager.conf
Jan 31 09:38:07 gooseberry NetworkManager[3717]:  WEXT support is enabled
Jan 31 09:38:07 gooseberry kernel: [  161.635031] traps: NetworkManager[3717] 
general protection ip:469fee sp:7fff5abe7ba0 error:0 in 
NetworkManager[40+10d000]
Jan 31 09:38:07 gooseberry kernel: [  161.711343] init: network-manager main 
process (3717) killed by SEGV signal
Jan 31 09:38:07 gooseberry kernel: [  161.711364] init: network-manager main 
process ended, respawning
Jan 31 09:38:07 gooseberry NetworkManager[3722]:  NetworkManager (version 
0.9.8.8) is starting...
Jan 31 09:38:07 gooseberry NetworkManager[3722]:  Read config file 
/etc/NetworkManager/NetworkManager.conf
Jan 31 09:38:07 gooseberry NetworkManager[3722]:  WEXT support is enabled
Jan 31 09:38:07 gooseberry kernel: [  161.717615] traps: NetworkManager[3722] 
general protection ip:469fee sp:7ffcad607d80 error:0 in 
NetworkManager[40+10d000]
Jan 31 09:38:07 gooseberry kernel: [  161.796157] init: network-manager main 
process (3722) killed by SEGV signal
Jan 31 09:38:07 gooseberry kernel: [  161.796179] init: network-manager main 
process ended, respawning
Jan 31 09:38:07 gooseberry NetworkManager[3727]:  NetworkManager (version 
0.9.8.8) is starting...
Jan 31 09:38:07 gooseberry NetworkManager[3727]:  Read config file 
/etc/NetworkManager/NetworkManager.conf
Jan 31 09:38:07 gooseberry NetworkManager[3727]:  WEXT support is enabled
Jan 31 09:38:07 gooseberry kernel: [  161.805741] traps: NetworkManager[3727] 
general protection ip:469fee sp:7ffd48e64d40 error:0 in 
NetworkManager[40+10d000]
Jan 31 09:38:07 gooseberry kernel: [  161.882233] init: network-manager main 
process (3727) killed by SEGV signal
Jan 31 09:38:07 gooseberry kernel: [  161.882247] init: network-manager main 
process ended, respawning
Jan 31 09:38:07 gooseberry NetworkManager[3732]:  NetworkManager (version 
0.9.8.8) is starting...
Jan 31 09:38:07 gooseberry NetworkManager[3732]:  Read config file 
/etc/NetworkManager/NetworkManager.conf
Jan 31 09:38:07 gooseberry NetworkManager[3732]:  WEXT support is enabled
Jan 31 09:38:07 gooseberry kernel: [  161.887065] traps: NetworkManager[3732] 
general protection ip:469fee sp:7ffe912d5d70 error:0 in 
NetworkManager[40+10d000]
Jan 31 09:38:07 gooseberry kernel: [  161.960756] init: network-

[Bug 468996] Re: Confusing method of launching

2016-01-26 Thread Vadim Peretokin
Yep, does not happen on 15.10:

vadi@vadi-HP-ZBook-14 ~ $ pydb
The program 'pydb' is currently not installed. You can install it by typing:
sudo apt-get install pydb
vadi@vadi-HP-ZBook-14 ~ $ sudo apt-get install pydb
[sudo] password for vadi: 
Reading package lists... Done
Building dependency tree   
Reading state information... Done
The following packages were automatically installed and are no longer required:
  fglrx-updates-core lib32gcc1 libc6-i386
Use 'apt-get autoremove' to remove them.
Suggested packages:
  ddd emacs22
The following NEW packages will be installed:
  pydb
0 to upgrade, 1 to newly install, 0 to remove and 0 not to upgrade.
Need to get 143 kB of archives.
After this operation, 606 kB of additional disk space will be used.
Get:1 http://mirror.internode.on.net/pub/ubuntu/ubuntu/ wily/universe pydb all 
1.26-1 [143 kB]
Fetched 143 kB in 0s (255 kB/s)
Selecting previously unselected package pydb.
(Reading database ... 287610 files and directories currently installed.)
Preparing to unpack .../archives/pydb_1.26-1_all.deb ...
Unpacking pydb (1.26-1) ...
Processing triggers for man-db (2.7.4-1) ...
Setting up pydb (1.26-1) ...
Install pydb for emacs
Processing triggers for python-support (1.0.15) ...
vadi@vadi-HP-ZBook-14 ~ $ pydb
(Pydb) q
vadi@vadi-HP-ZBook-14 ~ $

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/468996

Title:
  Confusing method of launching

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pydb/+bug/468996/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


  1   2   3   4   5   6   7   8   9   10   >