[Bug 1964453] Re: transgui 5.18.0+dfsg-1build1 doesn't work; error msg 'Duplicate object member: 'status"'

2022-03-28 Thread emk2203
The error is described in detail in https://github.com/transmission-
remote-gui/transgui/issues/1325 and https://github.com/transmission-
remote-gui/transgui/issues/1350.

It seems to be fixed for Arch systems but it's present for Debian/Ubuntu
systems. The first link should describe a fix as well. The error shows
only on connection to Transmission 3.00 daemons, Transmission 2.94
daemons don't have this issue according to Github issue #1325.

** Bug watch added: github.com/transmission-remote-gui/transgui/issues #1325
   https://github.com/transmission-remote-gui/transgui/issues/1325

** Bug watch added: github.com/transmission-remote-gui/transgui/issues #1350
   https://github.com/transmission-remote-gui/transgui/issues/1350

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

Title:
  transgui 5.18.0+dfsg-1build1 doesn't work; error msg 'Duplicate object
  member: 'status"'

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


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

[Bug 1964453] Re: transgui 5.18.0+dfsg-1build1 doesn't work; error msg 'Duplicate object member: 'status"'

2022-03-10 Thread emk2203
Now confirmed for a second system, both running Kubuntu 22.04
(2022-03-10)

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

Title:
  transgui 5.18.0+dfsg-1build1 doesn't work; error msg 'Duplicate object
  member: 'status"'

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


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

[Bug 1964453] [NEW] transgui 5.18.0+dfsg-1build1 doesn't work; error msg 'Duplicate object member: 'status"'

2022-03-10 Thread emk2203
Public bug reported:

Updated transgui (5.18.0+dfsg-1build1) from (5.18.0+dfsg-1) ...

After installation, opening of transgui gives error message 'Duplicate
object member: 'status"' on start. After clicking 'OK', attempt to
reload a config gives again the error msg, no action taken.

** Affects: transgui (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/1964453

Title:
  transgui 5.18.0+dfsg-1build1 doesn't work; error msg 'Duplicate object
  member: 'status"'

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


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

[Bug 1944026] [NEW] After stopping pulseaudio-dlna, errors occur

2021-09-18 Thread emk2203
Public bug reported:

System: Impish Indri from 2021-09-18, pulseaudio-dlna
0.5.3+git20200929-0.1

After shutting down pulseaudio-dlna with Ctrl-C, errors occur:

^CApplication is shutting down ...
09-18 10:22:32 pulseaudio_dlna.pulseaudio INFO 
PulseWatcher.shutdown()
09-18 10:22:32 pulseaudio_dlna.holder INFO 
Holder.shutdown()
09-18 10:22:32 pulseaudio_dlna.streamserver   INFO 
StreamServer GobjectMainLoopMixin.shutdown()
09-18 10:22:32 pulseaudio_dlna.pulseaudio INFO Remove 
"vsxs520d_dlna" sink ...
Process Process-3:
Traceback (most recent call last):
  File "/usr/lib/python3.9/multiprocessing/process.py", line 315, in _bootstrap
self.run()
  File "/usr/lib/python3.9/multiprocessing/process.py", line 108, in run
self._target(*self._args, **self._kwargs)
  File "/usr/lib/python3/dist-packages/pulseaudio_dlna/holder.py", line 67, in 
search
time.sleep(0.1)
KeyboardInterrupt

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "/usr/lib/python3.9/multiprocessing/process.py", line 318, in _bootstrap
util._exit_function()
  File "/usr/lib/python3.9/multiprocessing/util.py", line 360, in _exit_function
_run_finalizers()
  File "/usr/lib/python3.9/multiprocessing/util.py", line 300, in 
_run_finalizers
finalizer()
  File "/usr/lib/python3.9/multiprocessing/util.py", line 224, in __call__
res = self._callback(*self._args, **self._kwargs)
  File "/usr/lib/python3.9/multiprocessing/queues.py", line 201, in 
_finalize_join
thread.join()
  File "/usr/lib/python3.9/threading.py", line 1053, in join
self._wait_for_tstate_lock()
  File "/usr/lib/python3.9/threading.py", line 1069, in _wait_for_tstate_lock
elif lock.acquire(block, timeout):
KeyboardInterrupt

** Affects: pulseaudio-dlna (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/1944026

Title:
  After stopping pulseaudio-dlna, errors occur

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


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

[Bug 1944025] Re: pychromecast in pulseaudio-dlna fails to work

2021-09-18 Thread emk2203
System this is running on: recent Impish Indri from 2021-09-18,
python3-pychromecast 7.7.1-2

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

Title:
  pychromecast in pulseaudio-dlna fails to work

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


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

[Bug 1944025] [NEW] pychromecast in pulseaudio-dlna fails to work

2021-09-18 Thread emk2203
Public bug reported:

Error messages after trying discovery with pulseaudio-dlna --create-
device-config:

09-18 09:43:40 pychromecast   INFO Querying 
device status
Exception in thread zeroconf-ServiceBrowser__googlecast._tcp.local.:
Traceback (most recent call last):
  File "/usr/lib/python3.9/threading.py", line 973, in _bootstrap_inner
self.run()
  File "/usr/lib/python3/dist-packages/zeroconf/__init__.py", line 1557, in run
self._service_state_changed.fire(
  File "/usr/lib/python3/dist-packages/zeroconf/__init__.py", line 1333, in fire
h(**kwargs)
  File "/usr/lib/python3/dist-packages/zeroconf/__init__.py", line 1427, in 
on_change

Error messages while running pulseaudio-dlna:

9-18 09:48:25 pychromecast   INFO Querying 
device status
Exception in thread zeroconf-ServiceBrowser__googlecast._tcp.local.:
Traceback (most recent call last):
  File "/usr/lib/python3.9/threading.py", line 973, in _bootstrap_inner
self.run()
  File "/usr/lib/python3/dist-packages/zeroconf/__init__.py", line 1557, in run
self._service_state_changed.fire(
  File "/usr/lib/python3/dist-packages/zeroconf/__init__.py", line 1333, in fire
h(**kwargs)
  File "/usr/lib/python3/dist-packages/zeroconf/__init__.py", line 1427, in 
on_change
listener.add_service(*args)
  File "/usr/lib/python3/dist-packages/pychromecast/discovery.py", line 65, in 
add_service
self._add_update_service(zconf, typ, name, self.add_callback)
  File "/usr/lib/python3/dist-packages/pychromecast/discovery.py", line 123, in 
_add_update_service
callback(uuid, name)
  File "/usr/lib/python3/dist-packages/pychromecast/__init__.py", line 246, in 
internal_callback
callback(
  File "/usr/lib/python3/dist-packages/pulseaudio_dlna/plugins/__init__.py", 
line 36, in wrapper
device = f(*args, **kwargs)
  File 
"/usr/lib/python3/dist-packages/pulseaudio_dlna/plugins/chromecast/__init__.py",
 line 47, in _on_device_added
return ChromecastRendererFactory.from_pychromecast(device)
  File 
"/usr/lib/python3/dist-packages/pulseaudio_dlna/plugins/chromecast/renderer.py",
 line 183, in from_pychromecast
ip=pychromecast.host,
AttributeError: 'Chromecast' object has no attribute 'host'

All this results in pulseaudio-dlna skipping all present Chromecast
devices and only showing the DLNA modules.

** Affects: pychromecast (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/1944025

Title:
  pychromecast in pulseaudio-dlna fails to work

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


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

[Bug 1915179] acpidump.txt

2021-02-09 Thread emk2203
apport information

** Attachment added: "acpidump.txt"
   
https://bugs.launchpad.net/bugs/1915179/+attachment/5462035/+files/acpidump.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/1915179

Title:
  5.10.0-14.15 doesn't boot from btrfs root fs

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

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

[Bug 1915179] WifiSyslog.txt

2021-02-09 Thread emk2203
apport information

** Attachment added: "WifiSyslog.txt"
   
https://bugs.launchpad.net/bugs/1915179/+attachment/5462034/+files/WifiSyslog.txt

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

Title:
  5.10.0-14.15 doesn't boot from btrfs root fs

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

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

[Bug 1915179] UdevDb.txt

2021-02-09 Thread emk2203
apport information

** Attachment added: "UdevDb.txt"
   https://bugs.launchpad.net/bugs/1915179/+attachment/5462033/+files/UdevDb.txt

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

Title:
  5.10.0-14.15 doesn't boot from btrfs root fs

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

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

[Bug 1915179] RfKill.txt

2021-02-09 Thread emk2203
apport information

** Attachment added: "RfKill.txt"
   https://bugs.launchpad.net/bugs/1915179/+attachment/5462032/+files/RfKill.txt

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

Title:
  5.10.0-14.15 doesn't boot from btrfs root fs

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

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

[Bug 1915179] PulseList.txt

2021-02-09 Thread emk2203
apport information

** Attachment added: "PulseList.txt"
   
https://bugs.launchpad.net/bugs/1915179/+attachment/5462031/+files/PulseList.txt

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

Title:
  5.10.0-14.15 doesn't boot from btrfs root fs

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

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

[Bug 1915179] ProcModules.txt

2021-02-09 Thread emk2203
apport information

** Attachment added: "ProcModules.txt"
   
https://bugs.launchpad.net/bugs/1915179/+attachment/5462030/+files/ProcModules.txt

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

Title:
  5.10.0-14.15 doesn't boot from btrfs root fs

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

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

[Bug 1915179] ProcEnviron.txt

2021-02-09 Thread emk2203
apport information

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

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

Title:
  5.10.0-14.15 doesn't boot from btrfs root fs

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

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

[Bug 1915179] ProcInterrupts.txt

2021-02-09 Thread emk2203
apport information

** Attachment added: "ProcInterrupts.txt"
   
https://bugs.launchpad.net/bugs/1915179/+attachment/5462029/+files/ProcInterrupts.txt

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

Title:
  5.10.0-14.15 doesn't boot from btrfs root fs

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

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

[Bug 1915179] ProcCpuinfoMinimal.txt

2021-02-09 Thread emk2203
apport information

** Attachment added: "ProcCpuinfoMinimal.txt"
   
https://bugs.launchpad.net/bugs/1915179/+attachment/5462027/+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/1915179

Title:
  5.10.0-14.15 doesn't boot from btrfs root fs

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

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

[Bug 1915179] ProcCpuinfo.txt

2021-02-09 Thread emk2203
apport information

** Attachment added: "ProcCpuinfo.txt"
   
https://bugs.launchpad.net/bugs/1915179/+attachment/5462026/+files/ProcCpuinfo.txt

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

Title:
  5.10.0-14.15 doesn't boot from btrfs root fs

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

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

[Bug 1915179] PaInfo.txt

2021-02-09 Thread emk2203
apport information

** Attachment added: "PaInfo.txt"
   https://bugs.launchpad.net/bugs/1915179/+attachment/5462025/+files/PaInfo.txt

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

Title:
  5.10.0-14.15 doesn't boot from btrfs root fs

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

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

[Bug 1915179] Lsusb-v.txt

2021-02-09 Thread emk2203
apport information

** Attachment added: "Lsusb-v.txt"
   
https://bugs.launchpad.net/bugs/1915179/+attachment/5462024/+files/Lsusb-v.txt

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

Title:
  5.10.0-14.15 doesn't boot from btrfs root fs

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

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

[Bug 1915179] Lsusb-t.txt

2021-02-09 Thread emk2203
apport information

** Attachment added: "Lsusb-t.txt"
   
https://bugs.launchpad.net/bugs/1915179/+attachment/5462023/+files/Lsusb-t.txt

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

Title:
  5.10.0-14.15 doesn't boot from btrfs root fs

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

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

[Bug 1915179] Lsusb.txt

2021-02-09 Thread emk2203
apport information

** Attachment added: "Lsusb.txt"
   https://bugs.launchpad.net/bugs/1915179/+attachment/5462022/+files/Lsusb.txt

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

Title:
  5.10.0-14.15 doesn't boot from btrfs root fs

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

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

[Bug 1915179] Lspci-vt.txt

2021-02-09 Thread emk2203
apport information

** Attachment added: "Lspci-vt.txt"
   
https://bugs.launchpad.net/bugs/1915179/+attachment/5462021/+files/Lspci-vt.txt

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

Title:
  5.10.0-14.15 doesn't boot from btrfs root fs

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

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

[Bug 1915179] Lspci.txt

2021-02-09 Thread emk2203
apport information

** Attachment added: "Lspci.txt"
   https://bugs.launchpad.net/bugs/1915179/+attachment/5462020/+files/Lspci.txt

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

Title:
  5.10.0-14.15 doesn't boot from btrfs root fs

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

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

[Bug 1915179] IwConfig.txt

2021-02-09 Thread emk2203
apport information

** Attachment added: "IwConfig.txt"
   
https://bugs.launchpad.net/bugs/1915179/+attachment/5462019/+files/IwConfig.txt

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

Title:
  5.10.0-14.15 doesn't boot from btrfs root fs

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

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

[Bug 1915179] CurrentDmesg.txt

2021-02-09 Thread emk2203
apport information

** Attachment added: "CurrentDmesg.txt"
   
https://bugs.launchpad.net/bugs/1915179/+attachment/5462018/+files/CurrentDmesg.txt

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

Title:
  5.10.0-14.15 doesn't boot from btrfs root fs

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

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

[Bug 1915179] CRDA.txt

2021-02-09 Thread emk2203
apport information

** Attachment added: "CRDA.txt"
   https://bugs.launchpad.net/bugs/1915179/+attachment/5462017/+files/CRDA.txt

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

Title:
  5.10.0-14.15 doesn't boot from btrfs root fs

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

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

[Bug 1915179] Re: 5.10.0-14.15 doesn't boot from btrfs root fs

2021-02-09 Thread emk2203
apport information

** Tags added: apport-collected hirsute

** Description changed:

  Kernel stops boot with panic; message is "can't find init". A manual
  addition on the kernel boot parameter line via /etc/default/grub doesn't
  help. It looks like the kernel can't access the file system.
  
  lsinitramfs /boot/initrd.img | grep btr shows btrfs module as part of
  the initrd.
  
- kernel 5.10.0-13.14 didn't have this problem. System boots from it
- without issues.
+ kernel 5.10.0-13.14 didn't have this problem. System boots from it without 
issues.
+ --- 
+ ProblemType: Bug
+ ApportVersion: 2.20.11-0ubuntu57
+ Architecture: amd64
+ AudioDevicesInUse:
+  USERPID ACCESS COMMAND
+  /dev/snd/controlC0:  erik   1566 F pulseaudio
+  /dev/snd/controlC1:  erik   1566 F pulseaudio
+ CasperMD5CheckResult: unknown
+ CurrentDesktop: KDE
+ DistroRelease: Ubuntu 21.04
+ InstallationDate: Installed on 2020-03-24 (322 days ago)
+ InstallationMedia: Kubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200324)
+ MachineType: Dell Inc. Latitude E6530
+ Package: linux (not installed)
+ ProcFB: 0 i915drmfb
+ ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.10.0-13-generic 
root=UUID=3889732d-ec13-4b68-84f9-f1da4272ff0f ro rootflags=subvol=@ quiet 
splash
+ ProcVersionSignature: Ubuntu 5.10.0-13.14-generic 5.10.9
+ RelatedPackageVersions:
+  linux-restricted-modules-5.10.0-13-generic N/A
+  linux-backports-modules-5.10.0-13-generic  N/A
+  linux-firmware 1.194
+ Tags:  hirsute
+ Uname: Linux 5.10.0-13-generic x86_64
+ UpgradeStatus: No upgrade log present (probably fresh install)
+ UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo video
+ _MarkForUpload: True
+ dmi.bios.date: 11/30/2018
+ dmi.bios.release: 4.6
+ dmi.bios.vendor: Dell Inc.
+ dmi.bios.version: A22
+ dmi.board.name: 07Y85M
+ dmi.board.vendor: Dell Inc.
+ dmi.board.version: A00
+ dmi.chassis.type: 9
+ dmi.chassis.vendor: Dell Inc.
+ dmi.modalias: 
dmi:bvnDellInc.:bvrA22:bd11/30/2018:br4.6:svnDellInc.:pnLatitudeE6530:pvr01:rvnDellInc.:rn07Y85M:rvrA00:cvnDellInc.:ct9:cvr:
+ dmi.product.name: Latitude E6530
+ dmi.product.sku: Latitude E6530
+ dmi.product.version: 01
+ dmi.sys.vendor: Dell Inc.

** Attachment added: "AlsaInfo.txt"
   
https://bugs.launchpad.net/bugs/1915179/+attachment/5462016/+files/AlsaInfo.txt

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

Title:
  5.10.0-14.15 doesn't boot from btrfs root fs

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

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

[Bug 1915179] [NEW] 5.10.0-14.15 doesn't boot from btrfs root fs

2021-02-09 Thread emk2203
Public bug reported:

Kernel stops boot with panic; message is "can't find init". A manual
addition on the kernel boot parameter line via /etc/default/grub doesn't
help. It looks like the kernel can't access the file system.

lsinitramfs /boot/initrd.img | grep btr shows btrfs module as part of
the initrd.

kernel 5.10.0-13.14 didn't have this problem. System boots from it
without issues.

** 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/1915179

Title:
  5.10.0-14.15 doesn't boot from btrfs root fs

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

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

[Bug 1910114] [NEW] bash-completion doesn't expand all possible okular filetypes

2021-01-04 Thread emk2203
Public bug reported:

Since 2019, `okular` has gained the capability to open 7-zip compressed
comic book archives with the extension of .cb7 | .CB7 .

`bash-completion` is not keeping track.

Proposal: Change the okular install_xspec line in `/usr/share/bash-
completion/bash_completion` to

_install_xspec
'!*.@(okular|@(?(e|x)ps|?(E|X)PS|[pf]df|[PF]DF|dvi|DVI|cb[rz7]|CB[RZ7]|djv?(u)|DJV?(U)|dvi|DVI|gif|jp?(e)g|miff|tif?(f)|pn[gm]|p[bgp]m|bmp|xpm|ico|xwd|tga|pcx|GIF|JP?(E)G|MIFF|TIF?(F)|PN[GM]|P[BGP]M|BMP|XPM|ICO|XWD|TGA|PCX|epub|EPUB|odt|ODT|fb?(2)|FB?(2)|mobi|MOBI|g3|G3|chm|CHM)?(.?(gz|GZ|bz2|BZ2|xz|XZ)))'
okular

changing essentially from ...cb[rz]|CB[rz]... to ...cb[rz7]|CB[RZ7]... .

** Affects: bash-completion (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/1910114

Title:
  bash-completion doesn't expand all possible okular filetypes

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bash-completion/+bug/1910114/+subscriptions

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

[Bug 1904326] [NEW] During discovery, non-critical error occurs

2020-11-15 Thread emk2203
Public bug reported:

During discovery with `pulseaudio-dlna --create-device-config`, I get
the following non-critical error:

```bash
Exception in thread Thread-10:
Traceback (most recent call last):
  File "/usr/lib/python3.8/threading.py", line 932, in _bootstrap_inner
self.run()
  File "/usr/lib/python3.8/threading.py", line 1254, in run
self.function(*self.args, **self.kwargs)
TypeError: 'ServiceBrowser' object is not callable
```

Program plays music as expected with pulseaudio-dlna.

System is Kubuntu 21.04 (basically identical to 20.10 at the moment).
pulseaudio-dlna was installed from the official Ubuntu repo.

Version: pulseaudio-dlna 0.5.3+git20200329-0.1

Bug was reported upstream as well, but is maybe better fixed here.

** Affects: pulseaudio-dlna (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/1904326

Title:
  During discovery, non-critical error occurs

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

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

[Bug 1548206] Re: Kate spellcheck not working

2020-06-15 Thread emk2203
Still not fixed.

kate jp_20200316.txt
Hspell: can't open /usr/share/hspell/hebrew.wgz.sizes.
sonnet.plugins.hspell: HSpellDict::HSpellDict: Init failed

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

Title:
  Kate spellcheck not working

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

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

[Bug 1880100] [NEW] On ARM systems, package error stops any system upgrade

2020-05-22 Thread emk2203
Public bug reported:

After system install on an ARM system (Orange Pi Zero), an attempt to
update the system via `apt full-upgrade` results in the following error:

Traceback (most recent call last):
  File "/usr/lib/cnf-update-db", line 26, in 
col.create(db)
  File "/usr/lib/python3/dist-packages/CommandNotFound/db/creator.py", line 93, 
in create
self._fill_commands(con)
  File "/usr/lib/python3/dist-packages/CommandNotFound/db/creator.py", line 
127, in _fill_commands
self._parse_single_commands_file(con, fp)
  File "/usr/lib/python3/dist-packages/CommandNotFound/db/creator.py", line 
165, in _parse_single_commands_file
suite=tagf.section["suite"]
KeyError: 'suite'

Quick fix for me was to remove the package with `sudo apt purge command-
not-found && sudo apt --purge autoremove`. Reinstall of the package
leads to the same results.

command-not-found version: 20.04.2
Version table:
 20.04.2 500
500 http://ports.ubuntu.com focal/main armhf Packages

python --version: command not found
python3 --version: Python 3.8.2

** Affects: command-not-found (Ubuntu)
 Importance: Undecided
 Status: New

** Description changed:

  After system install on an ARM system (Orange Pi Zero), an attempt to
  update the system via `apt full-upgrade` results in the following error:
  
  Traceback (most recent call last):
-   File "/usr/lib/cnf-update-db", line 26, in 
- col.create(db)
-   File "/usr/lib/python3/dist-packages/CommandNotFound/db/creator.py", line 
93, in create
- self._fill_commands(con)
-   File "/usr/lib/python3/dist-packages/CommandNotFound/db/creator.py", line 
127, in _fill_commands
- self._parse_single_commands_file(con, fp)
-   File "/usr/lib/python3/dist-packages/CommandNotFound/db/creator.py", line 
165, in _parse_single_commands_file
- suite=tagf.section["suite"]
+   File "/usr/lib/cnf-update-db", line 26, in 
+ col.create(db)
+   File "/usr/lib/python3/dist-packages/CommandNotFound/db/creator.py", line 
93, in create
+ self._fill_commands(con)
+   File "/usr/lib/python3/dist-packages/CommandNotFound/db/creator.py", line 
127, in _fill_commands
+ self._parse_single_commands_file(con, fp)
+   File "/usr/lib/python3/dist-packages/CommandNotFound/db/creator.py", line 
165, in _parse_single_commands_file
+ suite=tagf.section["suite"]
  KeyError: 'suite'
  
  Quick fix for me was to remove the package with `sudo apt purge command-
  not-found && sudo apt --purge autoremove`. Reinstall of the package
  leads to the same results.
  
  command-not-found version: 20.04.2
  Version table:
-  20.04.2 500
- 500 http://ports.ubuntu.com focal/main armhf Packages
+  20.04.2 500
+ 500 http://ports.ubuntu.com focal/main armhf Packages
+ 
+ python --version: command not found
+ python3 --version: Python 3.8.2

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

Title:
  On ARM systems, package error stops any system upgrade

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/command-not-found/+bug/1880100/+subscriptions

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

[Bug 1876453] [NEW] trash-cli depends on Python2, but is already Python3-compatible

2020-05-02 Thread emk2203
Public bug reported:

Install of `trash-cli` depends on Python2, but the version in 20.04LTS
is the same as on the developer github at
https://github.com/andreafrancia/trash-cli and is already
Python3-compatible.

Please ease the package restrictions or make it dependent on Python3.

** Affects: trash-cli (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/1876453

Title:
  trash-cli depends on Python2, but is already Python3-compatible

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/trash-cli/+bug/1876453/+subscriptions

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

[Bug 1855595] [NEW] CUPS fails to print to autodetected printers because of cups-browsed error

2019-12-08 Thread emk2203
Public bug reported:

When trying to autodetected IPP printers, print job stays in queue.

lpstat -l:

HP_LaserJet_CM1415fn_44A808_-23 erik 30720   So 08 Dez 2019 
15:50:20 CET
Status: No suitable destination host found by cups-browsed.
Alarme: resources-are-not-ready
in Warteschlange eingereiht für HP_LaserJet_CM1415fn_44A808_

Removing the print job, restarting cups-browsed with `service cups-
browsed restart` followed by `service cups restart` enables printing for
one print job; the next one fails again with the same issue.

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: cups-browsed 1.25.13-1
ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10
Uname: Linux 5.3.0-24-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.20.11-0ubuntu13
Architecture: amd64
CurrentDesktop: LXQt
Date: Sun Dec  8 16:06:02 2019
InstallationDate: Installed on 2019-10-19 (50 days ago)
InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20191019)
Lpstat:
 device for HP_LaserJet_CM1415fn_44A808_: 
implicitclass://HP_LaserJet_CM1415fn_44A808_/
 device for Samsung_C48x_Series_SEC84251900EE44_: 
implicitclass://Samsung_C48x_Series_SEC84251900EE44_/
MachineType: Dell Inc. Latitude E6530
Papersize: a4
PpdFiles:
 Error: command ['fgrep', '-H', '*NickName', 
'/etc/cups/ppd/HP_LaserJet_CM1415fn_44A808_.ppd', 
'/etc/cups/ppd/Samsung_C48x_Series_SEC84251900EE44_.ppd'] failed with exit code 
2: grep: /etc/cups/ppd/HP_LaserJet_CM1415fn_44A808_.ppd: Permission denied
 grep: /etc/cups/ppd/Samsung_C48x_Series_SEC84251900EE44_.ppd: Permission denied
ProcKernelCmdLine: BOOT_IMAGE=/BOOT/ubuntu_utwd0l@/vmlinuz-5.3.0-24-generic 
root=ZFS=rpool/ROOT/ubuntu_utwd0l ro quiet splash vt.handoff=1
SourcePackage: cups-filters
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 11/30/2018
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A22
dmi.board.name: 07Y85M
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 9
dmi.chassis.vendor: Dell Inc.
dmi.modalias: 
dmi:bvnDellInc.:bvrA22:bd11/30/2018:svnDellInc.:pnLatitudeE6530:pvr01:rvnDellInc.:rn07Y85M:rvrA00:cvnDellInc.:ct9:cvr:
dmi.product.name: Latitude E6530
dmi.product.sku: Latitude E6530
dmi.product.version: 01
dmi.sys.vendor: Dell Inc.

** Affects: cups-filters (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/1855595

Title:
  CUPS fails to print to autodetected printers because of cups-browsed
  error

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cups-filters/+bug/1855595/+subscriptions

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

Re: [Bug 1836400] Re: transgui is outdated; new upstream repo should be used

2019-10-30 Thread emk2203
After all these weeks, transmission-gui didn't crash on three different
systems for me (Kubuntu, Lubuntu, Ubuntu Eoan and now Focal dev). Very
happy with the ppa.

As an aside, I wanted to make you aware that the latest update to 5.18 has
done away with the need for the libssl-dev library. If you want to update
this for the upcoming LTS, I am willing to test again.

Best regards

Am Mo., 9. Sept. 2019 um 15:47 Uhr schrieb Andreas Noteng <
1836...@bugs.launchpad.net>:

> Good to hear! Too bad we missed the freeze, I doubt the release team
> will approve syncing after freeze when the change is this significant
> and the package has no bugs except this one assosiated to it.
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1836400
>
> Title:
>   transgui is outdated; new upstream repo should be used
>
> To manage notifications about this bug go to:
>
> https://bugs.launchpad.net/ubuntu/+source/transgui/+bug/1836400/+subscriptions
>

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

Title:
  transgui is outdated; new upstream repo should be used

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

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

[Bug 1849515] Re: package snapd (not installed) failed to install/upgrade: »installiertes snapd-Skript des Paketes post-removal«-Unterprozess gab den Fehlerwert 1 zurück

2019-10-25 Thread emk2203
Workaround:

- unmount zfs volume 'sudo /var/snapd'
- uninstall package 'sudo apt purge snapd'

is error-free

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

Title:
  package snapd (not installed) failed to install/upgrade:
  »installiertes snapd-Skript des Paketes post-removal«-Unterprozess gab
  den Fehlerwert 1 zurück

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

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

Re: [Bug 1849515] Re: package snapd (not installed) failed to install/upgrade: »installiertes snapd-Skript des Paketes post-removal«-Unterprozess gab den Fehlerwert 1 zurück

2019-10-25 Thread emk2203
Yes.

Ian Johnson <1849...@bugs.launchpad.net> schrieb am Mi., 23. Okt. 2019,
22:49:

> >From the dpkg terminal log I see this:
>
> ```
> rm: das Entfernen von '/var/snap' ist nicht möglich: Das Gerät oder die
> Ressource ist belegt
> ```
>
> which google translate tells me means:
>
> ```
> rm: the removal of `/var/snap` is not possible: The device or resource is
> busy
> ```
>
> It looks like this system has ZFS on the rootfs, is that correct?
>
> ** Changed in: snapd (Ubuntu)
>Status: New => Triaged
>
> ** Changed in: snapd (Ubuntu)
>Importance: Undecided => High
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1849515
>
> Title:
>   package snapd (not installed) failed to install/upgrade:
>   »installiertes snapd-Skript des Paketes post-removal«-Unterprozess gab
>   den Fehlerwert 1 zurück
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1849515/+subscriptions
>

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

Title:
  package snapd (not installed) failed to install/upgrade:
  »installiertes snapd-Skript des Paketes post-removal«-Unterprozess gab
  den Fehlerwert 1 zurück

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

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

[Bug 1849515] [NEW] package snapd (not installed) failed to install/upgrade: »installiertes snapd-Skript des Paketes post-removal«-Unterprozess gab den Fehlerwert 1 zurück

2019-10-23 Thread emk2203
Public bug reported:

Full deinstallation of snapd didn't go through, error as described. A
restart and `sudo apt -f install` didn't show further issues.

ProblemType: Package
DistroRelease: Ubuntu 20.04
Package: snapd (not installed)
ProcVersionSignature: Ubuntu 5.3.0-18.19-generic 5.3.1
Uname: Linux 5.3.0-18-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.20.11-0ubuntu8
AptOrdering:
 gnome-software-plugin-snap:amd64: Purge
 snapd:amd64: Purge
 NULL: ConfigurePending
 NULL: PurgePending
 NULL: ConfigurePending
Architecture: amd64
Date: Wed Oct 23 16:45:52 2019
ErrorMessage: »installiertes snapd-Skript des Paketes 
post-removal«-Unterprozess gab den Fehlerwert 1 zurück
InstallationDate: Installed on 2019-10-19 (3 days ago)
InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20191019)
Python3Details: /usr/bin/python3.7, Python 3.7.5, python3-minimal, 3.7.5-1
PythonDetails: N/A
RelatedPackageVersions:
 dpkg 1.19.7ubuntu2
 apt  1.9.4
SourcePackage: snapd
Title: package snapd (not installed) failed to install/upgrade: »installiertes 
snapd-Skript des Paketes post-removal«-Unterprozess gab den Fehlerwert 1 zurück
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-package focal

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

Title:
  package snapd (not installed) failed to install/upgrade:
  »installiertes snapd-Skript des Paketes post-removal«-Unterprozess gab
  den Fehlerwert 1 zurück

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

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

[Bug 1848496] Re: [zfs-root] device-mapper: reload ioctl on osprober-linux-sda5 failed: Device or resource busy

2019-10-21 Thread emk2203
A try with
GRUB_OS_PROBER_SKIP_LIST="16144709171658112187@/dev/sda5"
in /etc/default/grub fails to work around the issue. The error remains.

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

Title:
  [zfs-root] device-mapper: reload ioctl on osprober-linux-sda5  failed:
  Device or resource busy

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/os-prober/+bug/1848496/+subscriptions

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

[Bug 1848496] Re: [zfs-root] device-mapper: reload ioctl on osprober-linux-sda5 failed: Device or resource busy

2019-10-21 Thread emk2203
In my setup, I have 2 partitions after the Ubuntu partition (sda5).
While update-grub runs through, the os-prober seems to abort and never
finds the following Windows 10 partition.

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

Title:
  [zfs-root] device-mapper: reload ioctl on osprober-linux-sda5  failed:
  Device or resource busy

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/os-prober/+bug/1848496/+subscriptions

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

[Bug 1846458] [NEW] On zfs-on-root system, grub fails to update from 2.04-1ubuntu6 to 2.04-1ubuntu8

2019-10-03 Thread emk2203
Public bug reported:

On a zfs-on-root system with eoan-proposed enabled, an update of grub-
efi to 2.04-1ubuntu8 from 2.04-1ubuntu6 failed due to a syntax error in
the generated /boot/grub/grub.cfg.new file - unexpected "}" in line 255.

Downgrading to 2.04-1ubuntu6 remedied the issue.

A Kubuntu system without zfs was unaffected and installed 2.04-1ubuntu8
without problems.

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

** Description changed:

  On a zfs-on-root system with eoan-proposed enabled, an update of grub-
  efi to 2.04-1ubuntu8 from 2.04-1ubuntu6 failed due to a syntax error in
- the generated /boot/grub/grub.cfg.new file.
+ the generated /boot/grub/grub.cfg.new file - unexpected "}" in line 255.
  
  Downgrading to 2.04-1ubuntu6 remedied the issue.
  
  A Kubuntu system without zfs was unaffected and installed 2.04-1ubuntu8
  without problems.

** Summary changed:

- On zfs system, grub fails to update [2.04-1ubuntu8]
+ On zfs-on-root system, grub fails to update from 2.04-1ubuntu6 to 
2.04-1ubuntu8

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

Title:
  On zfs-on-root system, grub fails to update from 2.04-1ubuntu6 to
  2.04-1ubuntu8

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

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

Re: [Bug 1836400] Re: transgui is outdated; new upstream repo should be used

2019-09-08 Thread emk2203
I downloaded and installed the package, so far, I don't see the sporadic
crashes from before on plain Ubuntu (Lubuntu and Kubuntu weren't affected).

Am So., 8. Sept. 2019 um 10:22 Uhr schrieb Bug Watch Updater <
1836...@bugs.launchpad.net>:

> ** Changed in: transgui (Debian)
>Status: New => Fix Released
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1836400
>
> Title:
>   transgui is outdated; new upstream repo should be used
>
> To manage notifications about this bug go to:
>
> https://bugs.launchpad.net/ubuntu/+source/transgui/+bug/1836400/+subscriptions
>

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

Title:
  transgui is outdated; new upstream repo should be used

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

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

[Bug 1836400] Re: transgui is outdated; new upstream repo should be used

2019-09-06 Thread emk2203
I am running mostly Eoan on the workstations now (it's already in
feature freeze, beta in 3 weeks).

Either plain, or the Lubuntu variant.

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

Title:
  transgui is outdated; new upstream repo should be used

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

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

[Bug 1836400] Re: transgui is outdated; new upstream repo should be used

2019-09-06 Thread emk2203
What's the best way to report bugs? The usual system doesn't work since
it's not an official package. I have transmission crash when the
computer is running for some time. It works if I start it directly after
boot.

Is it OK to attach the contents of /var/crash?

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

Title:
  transgui is outdated; new upstream repo should be used

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

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

Re: [Bug 1836400] Re: transgui is outdated; new upstream repo should be used

2019-09-03 Thread emk2203
I am trying to test in this week and let you know after a few days of
testing. Usually, it needs some workload changes with regard to number of
torrents, download/upload for issues to manifest in my experience.


Am Mi., 24. Juli 2019 um 00:05 Uhr schrieb Andreas Noteng <
1836...@bugs.launchpad.net>:

> I have created a preliminary package attached here. Would you please test
> it?
> So for it looks like SSL support isn't working, but it hasn't for a while
> anyways. We may have to remove SSL support alltogether in order to comply
> with some licencing issues:
> https://github.com/transmission-remote-gui/transgui/issues/1239
>
>
> ** Bug watch added: github.com/transmission-remote-gui/transgui/issues
> #1239
>https://github.com/transmission-remote-gui/transgui/issues/1239
>
> ** Attachment added: "test package"
>
> https://bugs.launchpad.net/ubuntu/+source/transgui/+bug/1836400/+attachment/5278768/+files/transgui_5.17.0.tar.xz
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1836400
>
> Title:
>   transgui is outdated; new upstream repo should be used
>
> To manage notifications about this bug go to:
>
> https://bugs.launchpad.net/ubuntu/+source/transgui/+bug/1836400/+subscriptions
>

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

Title:
  transgui is outdated; new upstream repo should be used

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

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

Re: [Bug 1836400] Re: transgui is outdated; new upstream repo should be used

2019-07-15 Thread emk2203
Thanks for the detailed explanation.

I have looked at this purely from a passive downloader perspective. For me,
the sourceforge repo from Mr Sidorov has always looked stale to me, since
the last change in downloadable files really is from 4 Jan 2014, in the
5.0.1 folder dated from 20 May 2015.

So, I assumed this to be dead (no activity for more than 5 years now).

The github repo has decent activity, I can't really tell if they are
windows-focused, but they do offer a Linux version, which runs very well on
my Eoan system here. I am willing to install this on a couple other systems
of mine if you need more feedback from a user perspective.

In terms of stability and day-to-day usage, it is much better than the
5.0.1 version, which used to hang sometimes and had noticeable delays.
These are gone now.

Hope this helps
Erik Koennecke

Am Fr., 12. Juli 2019 um 21:18 Uhr schrieb Andreas Noteng <
1836...@bugs.launchpad.net>:

> The upstream of the transgui currently in Debian and derivatives is this
> one: https://sourceforge.net/projects/transgui/
> The upstream you are referring to is a fork of this project. I have been
> in contact with both upstreams and previously considered changing sources.
> I my opinion the project you are referring to should have released under
> another name since Mr Sidorov has not abandoned his original project.
>
> Last time I looked at the fork, development seemed to have shifted focus
> towards Windows with little or no testing and development being done for
> Linux. This may have changed since last time I looked, and I am willing
> to reconsider my previous decision to not switch upstreams. The original
> project have not seen any action since 2017, and that certainly speaks
> in favor of the fork in github. That being said, the original upstream
> has always helped me fix bugs as needed in Debian and Ubuntu.
>
> I'd appreciate arguments pro et contra from experienced Ubuntu and/or
> Debian developers before making a decission to switch.
>
> ** Changed in: transgui (Ubuntu)
>Importance: Undecided => Wishlist
>
> ** Changed in: transgui (Ubuntu)
>Status: New => Opinion
>
> ** Bug watch added: Debian Bug tracker #897088
>https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=897088
>
> ** Also affects: transgui (Debian) via
>https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=897088
>Importance: Unknown
>Status: Unknown
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1836400
>
> Title:
>   transgui is outdated; new upstream repo should be used
>
> To manage notifications about this bug go to:
>
> https://bugs.launchpad.net/ubuntu/+source/transgui/+bug/1836400/+subscriptions
>

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

Title:
  transgui is outdated; new upstream repo should be used

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

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

[Bug 1836400] [NEW] transgui is outdated; new upstream repo should be used

2019-07-12 Thread emk2203
Public bug reported:

The old repo at code.google.com is abandoned, new repo is at
https://github.com/transmission-remote-gui/transgui with the latest
version 5.17.0 instead of 5.0.1 in Trusty to Eoan. Current 5.17.0 needs
libssl-dev in addition to the transgui binary for correct operation.

** Affects: transgui (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/1836400

Title:
  transgui is outdated; new upstream repo should be used

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

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

[Bug 1820695] Re: 5.0.0 kernels (5.0.0-7 and 5.0.0-8) don't boot

2019-04-16 Thread emk2203
It's not a kernel bug. The nvidia driver keeps the contents of the GRUB
screen and the first two lines of kernel log visible as a frozen static
picture.

Deinstall and reinstall of nvidia drivers fixed the issue.

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

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

Title:
  5.0.0 kernels (5.0.0-7 and 5.0.0-8) don't boot

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

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

[Bug 1820695] Re: 5.0.0 kernels (5.0.0-7 and 5.0.0-8) don't boot

2019-03-28 Thread emk2203
The kernel 5.1.0-050100rc1 boots successfully, but it's necessary for my
system to log in via ssh since the nvidia driver is missing.

Is bisection still necessary (it's a lot of work) when we know that 5.1
boots fine? I can wait until there's a 5.1 kernel and do with 4.19 until
then.

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

Title:
  5.0.0 kernels (5.0.0-7 and 5.0.0-8) don't boot

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

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

[Bug 1820695] Re: 5.0.0 kernels (5.0.0-7 and 5.0.0-8) don't boot

2019-03-18 Thread emk2203
The kernel 5.1.0-050100rc1-generic does boot for a short moment but
freezes before the login screen appears.

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

Title:
  5.0.0 kernels (5.0.0-7 and 5.0.0-8) don't boot

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

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

[Bug 1820695] Re: 5.0.0 kernels (5.0.0-7 and 5.0.0-8) don't boot

2019-03-18 Thread emk2203
** Attachment added: "dmesg.log"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1820695/+attachment/5247355/+files/dmesg.log

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

Title:
  5.0.0 kernels (5.0.0-7 and 5.0.0-8) don't boot

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

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

[Bug 1820695] Re: 5.0.0 kernels (5.0.0-7 and 5.0.0-8) don't boot

2019-03-18 Thread emk2203
** Attachment added: "uname-a.log"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1820695/+attachment/5247353/+files/uname-a.log

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

Title:
  5.0.0 kernels (5.0.0-7 and 5.0.0-8) don't boot

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

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

[Bug 1820695] [NEW] 5.0.0 kernels (5.0.0-7 and 5.0.0-8) don't boot

2019-03-18 Thread emk2203
Public bug reported:

System runs fine with previous kernel 4.19.0-13-generic. On kernels
5.0.0-7 and 5.0.0-8, system freezes after GRUB screen on the background
picture.

Note: The attached logs are done with kernel 4.19.0-13-generic, since
the kernels in question don't even boot and give no chance to catch a
log.

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

** Attachment added: "version.log"
   
https://bugs.launchpad.net/bugs/1820695/+attachment/5247352/+files/version.log

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

Title:
  5.0.0 kernels (5.0.0-7 and 5.0.0-8) don't boot

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

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

[Bug 1820695] Re: 5.0.0 kernels (5.0.0-7 and 5.0.0-8) don't boot

2019-03-18 Thread emk2203
** Attachment added: "lspci-vvnn.log"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1820695/+attachment/5247354/+files/lspci-vvnn.log

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

Title:
  5.0.0 kernels (5.0.0-7 and 5.0.0-8) don't boot

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

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

[Bug 689127] Re: Asumes Python 3 version of subprocess module

2018-11-05 Thread emk2203
Package erroneously wants to force install of Python 2 if only Python 3
is installed on system, the fix should rather be to remove the Python 2
dependencies.

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

Title:
  Asumes Python 3 version of subprocess module

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

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

[Bug 1775599] [NEW] package falkon 3.0.1-0ubuntu0.1 failed to install/upgrade: Unterprozess installed falkon package post-installation script gab den Fehler-Ausgangsstatus 2 zurück

2018-06-07 Thread emk2203
Public bug reported:

falkon (3.0.1-0ubuntu0.1) wird eingerichtet ...
update-alternatives: Fehler: Alternativen-Pfad /usr/bin/falkon existiert nicht
dpkg: Fehler beim Bearbeiten des Paketes falkon (--configure):
 Unterprozess installed falkon package post-installation script gab den 
Fehler-Ausgangsstatus 2 zurück

ProblemType: Package
DistroRelease: Ubuntu 18.04
Package: falkon 3.0.1-0ubuntu0.1
ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18
Uname: Linux 4.15.0-23-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.2
Architecture: amd64
Date: Thu Jun  7 14:45:34 2018
ErrorMessage: Unterprozess installed falkon package post-installation script 
gab den Fehler-Ausgangsstatus 2 zurück
Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3
PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 
2.7.15~rc1-1
RelatedPackageVersions:
 dpkg 1.19.0.5ubuntu2
 apt  1.6.1
SourcePackage: falkon
Title: package falkon 3.0.1-0ubuntu0.1 failed to install/upgrade: Unterprozess 
installed falkon package post-installation script gab den Fehler-Ausgangsstatus 
2 zurück
UpgradeStatus: Upgraded to bionic on 2017-06-03 (369 days ago)

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


** Tags: amd64 apport-package bionic package-from-proposed

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

Title:
  package falkon 3.0.1-0ubuntu0.1 failed to install/upgrade:
  Unterprozess installed falkon package post-installation script gab den
  Fehler-Ausgangsstatus 2 zurück

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

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

Re: [Bug 1708922] Re: uvcvideo module does not work with Dell XPS 12 webcam

2018-05-27 Thread emk2203
Ok, I will do that.

Reinhard Tartler <siret...@gmail.com> schrieb am Do., 12. Apr. 2018,
23:29:

> If you can, please file a separate bug for uvcvideo with a stacktrace. Then
> please link those bugs
>
> The easiest way is probably by using apport on the crash file, I guess.
>
> On Thu, Apr 12, 2018, 17:21 emk2203 <1708...@bugs.launchpad.net> wrote:
>
> > Original reporter here. I am willing to assist wherever I can, but I
> > reported chiefly because I cannot debug or investigate of my own.
> >
> > Regarding the cheese issue, the exact same issue arises when just using
> > uvcvideo, so it is definitely something passed on from the driver.
> >
> > 2018-04-12 15:52 GMT+02:00 Reinhard Tartler <siret...@gmail.com>:
> >
> > > Looking at the stacktrace, this is coming from /usr/bin/cheese. Even
> > > with bad input from the driver (which seems like a valid issue to
> > > investigate and improve) - an error message is preferable to a SIGFPE
> as
> > > seen in the initial report.
> > >
> > > ** Also affects: linux via
> > >https://trac.ffmpeg.org/ticket/4795
> > >Importance: Unknown
> > >Status: Unknown
> > >
> > > ** No longer affects: linux
> > >
> > > ** Changed in: ffmpeg (Ubuntu)
> > >Importance: Undecided => Low
> > >
> > > ** Also affects: cheese (Ubuntu)
> > >Importance: Undecided
> > >Status: New
> > >
> > > ** Changed in: cheese (Ubuntu)
> > >Importance: Undecided => Medium
> > >
> > > ** Changed in: cheese (Ubuntu)
> > >Status: New => Confirmed
> > >
> > > --
> > > You received this bug notification because you are subscribed to the
> bug
> > > report.
> > > https://bugs.launchpad.net/bugs/1708922
> > >
> > > Title:
> > >   uvcvideo module does not work with Dell XPS 12 webcam
> > >
> > > To manage notifications about this bug go to:
> > > https://bugs.launchpad.net/ubuntu/+source/cheese/+bug/
> > > 1708922/+subscriptions
> > >
> >
> > --
> > You received this bug notification because you are a member of MOTU
> > Media Team, which is subscribed to ffmpeg in Ubuntu.
> > https://bugs.launchpad.net/bugs/1708922
> >
> > Title:
> >   uvcvideo module does not work with Dell XPS 12 webcam
> >
> > To manage notifications about this bug go to:
> >
> >
> https://bugs.launchpad.net/ubuntu/+source/cheese/+bug/1708922/+subscriptions
> >
> > Launchpad-Notification-Type: bug
> > Launchpad-Bug: distribution=ubuntu; sourcepackage=cheese; component=main;
> > status=Confirmed; importance=Medium; assignee=None;
> > Launchpad-Bug: distribution=ubuntu; sourcepackage=ffmpeg;
> > component=universe; status=Incomplete; importance=Low; assignee=None;
> > Launchpad-Bug: distribution=ubuntu; sourcepackage=linux; component=main;
> > status=Incomplete; importance=Medium; assignee=None;
> > Launchpad-Bug-Tags: amd64 apport-crash artful gstreamer-error
> > Launchpad-Bug-Information-Type: Public
> > Launchpad-Bug-Private: no
> > Launchpad-Bug-Security-Vulnerability: no
> > Launchpad-Bug-Commenters: apport emk2203 janitor jcowgill kaihengfeng
> > siretart ubuntu-kernel-bot
> > Launchpad-Bug-Reporter: emk2203 (emk2203)
> > Launchpad-Bug-Modifier: emk2203 (emk2203)
> > Launchpad-Message-Rationale: Subscriber (ffmpeg in Ubuntu) @motumedia
> > Launchpad-Message-For: motumedia
> >
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1708922
>
> Title:
>   uvcvideo module does not work with Dell XPS 12 webcam
>
> To manage notifications about this bug go to:
>
> https://bugs.launchpad.net/ubuntu/+source/cheese/+bug/1708922/+subscriptions
>

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

Title:
  uvcvideo module does not work with Dell XPS 12 webcam

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

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

[Bug 1750264] Re: program 'cd-paranoia' is missing from package in 1.0.0-2

2018-05-16 Thread emk2203
For anyone who wants a fix independent from Ubuntu maintainers action:

Go to the deb multimedia repo for unstable sid and download 
http://www.deb-multimedia.org/dists/unstable/main/binary-amd64/package/cd-paranoia
 and 
http://www.deb-multimedia.org/dists/unstable/main/binary-amd64/package/libcdio18.php
 .

Install with `dpkg -i`, done. Two harmless error messages are thrown
when the program runs, they can be safely ignored.


Errors to ignore:
cd-paranoia: /usr/lib/x86_64-linux-gnu/libcdio_paranoia.so.2: no version 
information available (required by cd-paranoia)
cd-paranoia: /usr/lib/x86_64-linux-gnu/libcdio_cdda.so.2: no version 
information available (required by cd-paranoia)

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

Title:
  program 'cd-paranoia' is missing from package in 1.0.0-2

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

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

[Bug 1750264] Re: program 'cd-paranoia' is missing from package in 1.0.0-2

2018-04-14 Thread emk2203
The solution would be to just set the binary to be installed in the
install file. Independent from the decision of deb multimedia. Workable
solution with the least amount of effort.

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

Title:
  program 'cd-paranoia' is missing from package in 1.0.0-2

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

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

Re: [Bug 1708922] Re: uvcvideo module does not work with Dell XPS 12 webcam

2018-04-12 Thread emk2203
Original reporter here. I am willing to assist wherever I can, but I
reported chiefly because I cannot debug or investigate of my own.

Regarding the cheese issue, the exact same issue arises when just using
uvcvideo, so it is definitely something passed on from the driver.

2018-04-12 15:52 GMT+02:00 Reinhard Tartler :

> Looking at the stacktrace, this is coming from /usr/bin/cheese. Even
> with bad input from the driver (which seems like a valid issue to
> investigate and improve) - an error message is preferable to a SIGFPE as
> seen in the initial report.
>
> ** Also affects: linux via
>https://trac.ffmpeg.org/ticket/4795
>Importance: Unknown
>Status: Unknown
>
> ** No longer affects: linux
>
> ** Changed in: ffmpeg (Ubuntu)
>Importance: Undecided => Low
>
> ** Also affects: cheese (Ubuntu)
>Importance: Undecided
>Status: New
>
> ** Changed in: cheese (Ubuntu)
>Importance: Undecided => Medium
>
> ** Changed in: cheese (Ubuntu)
>Status: New => Confirmed
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1708922
>
> Title:
>   uvcvideo module does not work with Dell XPS 12 webcam
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/cheese/+bug/
> 1708922/+subscriptions
>

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

Title:
  uvcvideo module does not work with Dell XPS 12 webcam

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

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

[Bug 1756070] Re: watchdog: BUG: soft lockup - CPU#0 stuck for 23s! [Xorg:5557]

2018-03-26 Thread emk2203
Issue started after one of the updates. Prior kernel version difficult
to pinpoint, since the bug seems to happen only after cold boots, not
after a warm boot.

WORKAROUND: Start computer, restart after boot process completed.

4.16rc4 didn't show the symptoms, but was unusable since zfs is missing
from it.

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

Title:
  watchdog: BUG: soft lockup - CPU#0 stuck for 23s! [Xorg:5557]

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

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

[Bug 1756070] Re: watchdog: BUG: soft lockup - CPU#0 stuck for 23s! [Xorg:5557]

2018-03-25 Thread emk2203
** Tags added: kernel-fixed-upstream

** 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/1756070

Title:
  watchdog: BUG: soft lockup - CPU#0 stuck for 23s! [Xorg:5557]

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

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

[Bug 1756070] [NEW] watchdog: BUG: soft lockup - CPU#0 stuck for 23s! [Xorg:5557]

2018-03-15 Thread emk2203
Public bug reported:

after startup

ProblemType: KernelOops
DistroRelease: Ubuntu 18.04
Package: linux-image-4.15.0-12-generic 4.15.0-12.13
ProcVersionSignature: Ubuntu 4.15.0-12.13-generic 4.15.7
Uname: Linux 4.15.0-12-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_uvm 
nvidia_drm nvidia_modeset nvidia
Annotation: Your system might become unstable now and might need to be 
restarted.
ApportVersion: 2.20.8-0ubuntu10
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC1:  gdm5288 F pulseaudio
  erik   7152 F pulseaudio
 /dev/snd/controlC0:  gdm5288 F pulseaudio
  erik   7152 F pulseaudio
Date: Wed Mar 14 20:10:57 2018
Failure: oops
HibernationDevice: RESUME=UUID=fb731a76-d649-4283-9a48-91fda418f5d4
InstallationDate: Installed on 2018-02-25 (18 days ago)
InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180225)
IwConfig:
 enp3s0no wireless extensions.
 
 lono wireless extensions.
 
 enp8s0no wireless extensions.
MachineType: Gigabyte Technology Co., Ltd. To be filled by O.E.M.
ProcFB: 0 VESA VGA
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-12-generic 
root=UUID=269d199c-0dea-47bc-89fb-5388d4361c0e ro quiet splash vt.handoff=1
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
RelatedPackageVersions: kerneloops-daemon N/A
RfKill:
 
SourcePackage: linux
Title: watchdog: BUG: soft lockup - CPU#0 stuck for 23s! [Xorg:5557]
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 07/11/2016
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: U1n
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: Z68X-UD3H-B3
dmi.board.vendor: Gigabyte Technology Co., Ltd.
dmi.board.version: To be filled by O.E.M.
dmi.chassis.asset.tag: To Be Filled By O.E.M.
dmi.chassis.type: 3
dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
dmi.chassis.version: To Be Filled By O.E.M.
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrU1n:bd07/11/2016:svnGigabyteTechnologyCo.,Ltd.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnZ68X-UD3H-B3:rvrTobefilledbyO.E.M.:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.:
dmi.product.family: To be filled by O.E.M.
dmi.product.name: To be filled by O.E.M.
dmi.product.version: To be filled by O.E.M.
dmi.sys.vendor: Gigabyte Technology Co., Ltd.

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


** Tags: amd64 apport-kerneloops bionic kernel-oops

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

Title:
  watchdog: BUG: soft lockup - CPU#0 stuck for 23s! [Xorg:5557]

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

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

Re: [Bug 1751460] Re: [regression] deja-dup-monitor crashed with SIGSEGV in Gigacage::<lambda()>::operator()

2018-03-13 Thread emk2203
Am 13.03.2018 9:26 vorm. schrieb "Daniel van Vugt" <
daniel.van.v...@canonical.com>:

Workaround:

sudo apt remove deja-dup


Best idea so far. This program crashes consistently in every Ubuntu
distribution for years. I won't touch it with a ten-foot pole. Who would
trust it for something important like a backup?

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

Title:
  [regression] deja-dup-monitor crashed with SIGSEGV in
  Gigacage::::operator()

To manage notifications about this bug go to:
https://bugs.launchpad.net/deja-dup/+bug/1751460/+subscriptions

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

[Bug 1753745] [NEW] watchdog: BUG: soft lockup - CPU#0 stuck for 22s! [Xorg:4873]

2018-03-06 Thread emk2203
Public bug reported:

during startup or before cold boot. System used a lot of resources,
necessitating a reboot

ProblemType: KernelOops
DistroRelease: Ubuntu 18.04
Package: linux-image-4.15.0-11-generic 4.15.0-11.12
ProcVersionSignature: Ubuntu 4.15.0-11.12-generic 4.15.5
Uname: Linux 4.15.0-11-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_uvm 
nvidia_drm nvidia_modeset nvidia
Annotation: Your system might become unstable now and might need to be 
restarted.
ApportVersion: 2.20.8-0ubuntu10
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC1:  erik  22879 F pulseaudio
  gdm   31270 F pulseaudio
 /dev/snd/controlC0:  erik  22879 F pulseaudio
  gdm   31270 F pulseaudio
Date: Tue Mar  6 13:04:17 2018
Failure: oops
HibernationDevice: RESUME=UUID=fb731a76-d649-4283-9a48-91fda418f5d4
InstallationDate: Installed on 2018-02-25 (9 days ago)
InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180225)
IwConfig:
 enp3s0no wireless extensions.
 
 enp8s0no wireless extensions.
 
 lono wireless extensions.
MachineType: Gigabyte Technology Co., Ltd. To be filled by O.E.M.
ProcFB: 0 VESA VGA
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-11-generic 
root=UUID=269d199c-0dea-47bc-89fb-5388d4361c0e ro quiet splash vt.handoff=1
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
RelatedPackageVersions: kerneloops-daemon N/A
RfKill:
 
SourcePackage: linux
Title: watchdog: BUG: soft lockup - CPU#0 stuck for 22s! [Xorg:4873]
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 07/11/2016
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: U1n
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: Z68X-UD3H-B3
dmi.board.vendor: Gigabyte Technology Co., Ltd.
dmi.board.version: To be filled by O.E.M.
dmi.chassis.asset.tag: To Be Filled By O.E.M.
dmi.chassis.type: 3
dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
dmi.chassis.version: To Be Filled By O.E.M.
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrU1n:bd07/11/2016:svnGigabyteTechnologyCo.,Ltd.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnZ68X-UD3H-B3:rvrTobefilledbyO.E.M.:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.:
dmi.product.family: To be filled by O.E.M.
dmi.product.name: To be filled by O.E.M.
dmi.product.version: To be filled by O.E.M.
dmi.sys.vendor: Gigabyte Technology Co., Ltd.

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


** Tags: amd64 apport-kerneloops bionic kernel-oops package-from-proposed

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

Title:
  watchdog: BUG: soft lockup - CPU#0 stuck for 22s! [Xorg:4873]

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

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

[Bug 1752046] Re: curl now uses libcurl4 instead of libcurl3, which breaks megatools

2018-02-27 Thread emk2203
** Description changed:

  There is a conflict in 18.04 with curl and libcurl4, since megatools
  still uses libcurl3.
+ 
+ Bionic 18.04LTS

** Description changed:

  There is a conflict in 18.04 with curl and libcurl4, since megatools
- still uses libcurl3.
+ still uses libcurl3. curl wants to remove libcurl3 and install libcurl4
+ instead.
  
  Bionic 18.04LTS

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

Title:
  curl now uses libcurl4 instead of libcurl3, which breaks megatools

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

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

[Bug 1752050] [NEW] package conflict with curl

2018-02-27 Thread emk2203
Public bug reported:

whoopsie depends on libcurl3, while curl now wants to deinstall libcurl3
and install libcurl4.

Bionic 18.04LTS

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

** Description changed:

  whoopsie depends on libcurl3, while curl now wants to deinstall libcurl3
  and install libcurl4.
+ 
+ Bionic 18.04LTS

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

Title:
  package conflict with curl

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

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

[Bug 1752052] [NEW] package conflict with curl

2018-02-27 Thread emk2203
Public bug reported:

cmake depends on libcurl3, while curl wants to remove libcurl3 and
install libcurl4.

Bionic 18.04LTS

** Affects: cmake (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/1752052

Title:
  package conflict with curl

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

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

[Bug 1752046] [NEW] curl now uses libcurl4 instead of libcurl3, which breaks megatools

2018-02-27 Thread emk2203
Public bug reported:

There is a conflict in 18.04 with curl and libcurl4, since megatools
still uses libcurl3.

** Affects: megatools (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/1752046

Title:
  curl now uses libcurl4 instead of libcurl3, which breaks megatools

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

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

[Bug 1750264] [NEW] program 'cd-paranoia' is missing from package in 1.0.0-2

2018-02-18 Thread emk2203
Public bug reported:

apt show libcdio-utils:

Description: sample applications based on the CDIO libraries
 This package contains a collection of small libcdio-based tools:
  * cd-drive  show CD-ROM drive characteristics
  * cd-info   show information about a CD or CD-image
  * cd-paranoia   an audio CD ripper
  * cd-read   read information from a CD or CD-image
  * cdda-player   a simple curses-based audio CD player
  * iso-info  show information about an ISO 9660 image
  * iso-read  read portions of an ISO 9660 image
  * mmc-tool  issue low-level commands to a CD drive

cd-paranoia is missing from package. This breaks abcde 'optional'
functionality which is in fact the most common used, since the original
cdparanoia (separate program) is abandoned since 10 years.

Description:Ubuntu Bionic Beaver (development branch)
Release:18.04

libcdio-utils:
  Installiert:   1.0.0-2
  Installationskandidat: 1.0.0-2
  Versionstabelle:
 *** 1.0.0-2 500
500 http://de.archive.ubuntu.com/ubuntu bionic/universe amd64 Packages
100 /var/lib/dpkg/status

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: libcdio-utils 1.0.0-2
ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3
Uname: Linux 4.15.0-10-generic x86_64
ApportVersion: 2.20.8-0ubuntu10
Architecture: amd64
CurrentDesktop: LXQt
Date: Sun Feb 18 18:18:55 2018
ProcEnviron:
 TERM=qterminal
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=de_DE.UTF-8
 SHELL=/bin/bash
SourcePackage: libcdio
UpgradeStatus: Upgraded to bionic on 2017-06-03 (260 days ago)

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


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

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

Title:
  program 'cd-paranoia' is missing from package in 1.0.0-2

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

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

[Bug 1749137] [NEW] package lubuntu-default-settings 0.54 failed to install/upgrade: Versuch, »/usr/share/xsessions/QLubuntu.desktop« zu überschreiben, welches auch in Paket qlubuntu-default-session 0

2018-02-13 Thread emk2203
Public bug reported:

During apt dist-upgrade. Files in lubuntu-default-settings and QLubuntu-
default-settings conflict.

ProblemType: Package
DistroRelease: Ubuntu 18.04
Package: lubuntu-default-settings 0.54
ProcVersionSignature: Ubuntu 4.15.0-9.10-generic 4.15.2
Uname: Linux 4.15.0-9-generic x86_64
ApportVersion: 2.20.8-0ubuntu9
Architecture: amd64
Date: Tue Feb 13 10:16:31 2018
ErrorMessage: Versuch, »/usr/share/xsessions/QLubuntu.desktop« zu 
überschreiben, welches auch in Paket qlubuntu-default-session 0.53 ist
PackageArchitecture: all
Python3Details: /usr/bin/python3.6, Python 3.6.4+, python3-minimal, 3.6.4-1
PythonDetails: /usr/bin/python2.7, Python 2.7.14+, python-minimal, 2.7.14-4
RelatedPackageVersions:
 dpkg 1.19.0.5ubuntu1
 apt  1.6~alpha7ubuntu1
SourcePackage: lubuntu-default-settings
Title: package lubuntu-default-settings 0.54 failed to install/upgrade: 
Versuch, »/usr/share/xsessions/QLubuntu.desktop« zu überschreiben, welches auch 
in Paket qlubuntu-default-session 0.53 ist
UpgradeStatus: Upgraded to bionic on 2017-06-03 (255 days ago)

** Affects: lubuntu-default-settings (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-package bionic package-from-proposed third-party-packages

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

Title:
  package lubuntu-default-settings 0.54 failed to install/upgrade:
  Versuch, »/usr/share/xsessions/QLubuntu.desktop« zu überschreiben,
  welches auch in Paket qlubuntu-default-session 0.53 ist

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lubuntu-default-settings/+bug/1749137/+subscriptions

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

[Bug 1748992] [NEW] package gnome-menus 3.13.3-11ubuntu1 failed to install/upgrade: Trigger bilden eine Schleife, aufgegeben

2018-02-12 Thread emk2203
Public bug reported:

package reference looping occured, removal of package gnome-menus
removed two old unity packages and reinstall of gnome-menus went
smoothly.

ProblemType: Package
DistroRelease: Ubuntu 18.04
Package: gnome-menus 3.13.3-11ubuntu1
ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13
Uname: Linux 4.13.0-32-generic x86_64
ApportVersion: 2.20.8-0ubuntu8
Architecture: amd64
Date: Mon Feb 12 21:32:53 2018
Dependencies:
 
ErrorMessage: Trigger bilden eine Schleife, aufgegeben
InstallationDate: Installed on 2017-04-01 (317 days ago)
InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Beta amd64 (20170331)
Python3Details: /usr/bin/python3.6, Python 3.6.4, python3-minimal, 3.6.4-1
PythonDetails: /usr/bin/python2.7, Python 2.7.14+, python-minimal, 2.7.14-4
RelatedPackageVersions:
 dpkg 1.19.0.5ubuntu1
 apt  1.6~alpha7ubuntu1
SourcePackage: gnome-menus
Title: package gnome-menus 3.13.3-11ubuntu1 failed to install/upgrade: Trigger 
bilden eine Schleife, aufgegeben
UpgradeStatus: Upgraded to bionic on 2017-06-08 (249 days ago)

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


** Tags: amd64 apport-package bionic

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

Title:
  package gnome-menus 3.13.3-11ubuntu1 failed to install/upgrade:
  Trigger bilden eine Schleife, aufgegeben

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

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

[Bug 1748993] [NEW] package gnome-menus 3.13.3-11ubuntu1 failed to install/upgrade: Trigger bilden eine Schleife, aufgegeben

2018-02-12 Thread emk2203
*** This bug is a duplicate of bug 1748992 ***
https://bugs.launchpad.net/bugs/1748992

Public bug reported:

package reference looping occured, removal of package gnome-menus
removed two old unity packages and reinstall of gnome-menus went
smoothly.

ProblemType: Package
DistroRelease: Ubuntu 18.04
Package: gnome-menus 3.13.3-11ubuntu1
ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13
Uname: Linux 4.13.0-32-generic x86_64
ApportVersion: 2.20.8-0ubuntu8
Architecture: amd64
Date: Mon Feb 12 21:32:53 2018
Dependencies:
 
ErrorMessage: Trigger bilden eine Schleife, aufgegeben
InstallationDate: Installed on 2017-04-01 (317 days ago)
InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Beta amd64 (20170331)
Python3Details: /usr/bin/python3.6, Python 3.6.4, python3-minimal, 3.6.4-1
PythonDetails: /usr/bin/python2.7, Python 2.7.14+, python-minimal, 2.7.14-4
RelatedPackageVersions:
 dpkg 1.19.0.5ubuntu1
 apt  1.6~alpha7ubuntu1
SourcePackage: gnome-menus
Title: package gnome-menus 3.13.3-11ubuntu1 failed to install/upgrade: Trigger 
bilden eine Schleife, aufgegeben
UpgradeStatus: Upgraded to bionic on 2017-06-08 (249 days ago)

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


** Tags: amd64 apport-package bionic

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

Title:
  package gnome-menus 3.13.3-11ubuntu1 failed to install/upgrade:
  Trigger bilden eine Schleife, aufgegeben

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

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

[Bug 1739880] Re: on wayland, mpv opens without window elements, OSD missing

2017-12-29 Thread emk2203
Also, URL dropping works with 0.28.0 under wayland, but not file
dropping. This switch to 0.28.0 would take care of this bug (#1739880),
#1720835 and half of #1730625.

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

Title:
  on wayland, mpv opens without window elements, OSD missing

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

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

[Bug 1739880] Re: on wayland, mpv opens without window elements, OSD missing

2017-12-29 Thread emk2203
Another option would be to go to `mpv` 0.28.0. A test install from Doug
McMahon's mpv-tests ppa ppa:mc3man/mpv-tests shows that the current
version 0.28 works on wayland with OSD, window decoration and also menu
options working. No entries in mpv.conf needed.

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

Title:
  on wayland, mpv opens without window elements, OSD missing

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

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

[Bug 1739880] [NEW] on wayland, mpv opens without window elements, OSD missing

2017-12-23 Thread emk2203
Public bug reported:

Gnome/Wayland is the standard Ubuntu version, starting at 18.04LTS. A
standard mpv install here (0.27.0-2ubuntu4 from universe) will give a
mpv without window decorations or OSD, limiting mpv usability
significantly.

I propose to change the packaged mpv.conf in way that opengl-
backend=x11egl is included. This way, mpv works as expected in a
standard environment.

** Affects: mpv (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/1739880

Title:
  on wayland, mpv opens without window elements, OSD missing

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

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

Re: [Bug 1633737] Re: Anki fails to start in Yakkety due to missing PyQt4-WebKit

2017-11-20 Thread emk2203
​I would suggest to switch to Anki 2.1 beta
, which is in testing for over a
year now (beta 25 currently) and looks good enough.

It uses the latest dependencies (Python 3, Qt 5.9) and should be the future
of Anki.

Downside is that plugins for Anki need to be rewritten. I am not sure about
their status now, but even an Anki with limited plugin
availability is better than no Anki at all in the distribution.

Those who need more can alwas install the compiled package as Joshua Panter
suggested.

Erik Koennecke

Am 16.11.2017 1:59 nachm. schrieb "Joshua Panter" <
1633...@bugs.launchpad.net>:

> why not just package the compiled package from
> https://apps.ankiweb.net/? Has this been done, is there a repo with
> this?
>
> Can anybody confirm if #6 from above fixes the problem?
>
> --
> You received this bug notification because you are subscribed to a
> duplicate bug report (1660984).
> https://bugs.launchpad.net/bugs/1633737
>
> Title:
>   Anki fails to start in Yakkety due to missing PyQt4-WebKit
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/anki/+bug/1633737/+subscriptions
>

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

Title:
  Anki fails to start in Yakkety due to missing PyQt4-WebKit

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

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

[Bug 1710862] [NEW] Synaptics s3203 touchpad on Dell XPS12-9Q33 has no working buttons after recent upgrade

2017-08-15 Thread emk2203
Public bug reported:

The touchpad buttons don't work anymore after a recent system upgrade.
Cursor movement and tap options are unaffected - I get left button
functionality with a one-finger tap and right-button functionality with
a two-finger tap. Scrolling also works.

Hardware is OK (dual-boot shows that).

xev | grep -i button does not detect button presses, only if done by the
tap on the touchpad:

$ xev | grep -i button
ButtonPress event, serial 36, synthetic NO, window 0x401,
state 0x0, button 1, same_screen YES
ButtonRelease event, serial 36, synthetic NO, window 0x401,
state 0x100, button 1, same_screen YES
ButtonPress event, serial 36, synthetic NO, window 0x401,
state 0x0, button 3, same_screen YES
ButtonRelease event, serial 36, synthetic NO, window 0x401,
state 0x400, button 3, same_screen YES

System is running x11, but wayland didn't make a difference.


input: Synaptics s3203 as /devices/pci:00/INT33C3:00/i2c-8/i2c-
DLL05E3:01/0018:06CB:2734.0002/input/input14

ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: xserver-xorg-input-synaptics 1.9.0-1ubuntu1
ProcVersionSignature: Ubuntu 4.11.0-13.19-generic 4.11.12
Uname: Linux 4.11.0-13-generic x86_64
ApportVersion: 2.20.6-0ubuntu5
Architecture: amd64
CurrentDesktop: GNOME
Date: Tue Aug 15 12:59:26 2017
DistUpgraded: 2017-06-08 09:16:23,432 ERROR got error from PostInstallScript 
./xorg_fix_proprietary.py (g-exec-error-quark: Kindprozess 
»./xorg_fix_proprietary.py« konnte nicht ausgeführt werden (Datei oder 
Verzeichnis nicht gefunden) (8))
DistroCodename: artful
DistroVariant: ubuntu
InstallationDate: Installed on 2017-04-01 (136 days ago)
InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Beta amd64 (20170331)
MachineType: Dell Inc. XPS 12-9Q33
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=de_DE.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.11.0-13-generic.efi.signed 
root=UUID=1551b59c-7fbd-40f7-95c4-47d5359b39dc ro quiet splash vt.handoff=7
SourcePackage: xserver-xorg-input-synaptics
UpgradeStatus: Upgraded to artful on 2017-06-08 (68 days ago)
dmi.bios.date: 03/03/2015
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A08
dmi.board.name: XPS 12-9Q33
dmi.board.vendor: Dell Inc.
dmi.board.version: A08
dmi.chassis.type: 8
dmi.chassis.vendor: Dell Inc.
dmi.chassis.version: Not Specified
dmi.modalias: 
dmi:bvnDellInc.:bvrA08:bd03/03/2015:svnDellInc.:pnXPS12-9Q33:pvrA08:rvnDellInc.:rnXPS12-9Q33:rvrA08:cvnDellInc.:ct8:cvrNotSpecified:
dmi.product.name: XPS 12-9Q33
dmi.product.version: A08
dmi.sys.vendor: Dell Inc.
peripherals:
 /desktop/gnome/peripherals/Synaptics@32@s3203:
   device_type = touchpad
  /desktop/gnome/peripherals/PS@47@2@32@Synaptics@32@TouchPad:
   device_type = mouse
version.compiz: compiz 1:0.9.13.1+17.10.20170720-0ubuntu1
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.82-1
version.libgl1-mesa-dri: libgl1-mesa-dri 17.1.4-1ubuntu1
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 17.1.4-1ubuntu1
version.xserver-xorg-core: xserver-xorg-core 2:1.19.3-1ubuntu2
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.9.0-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20170309-0ubuntu1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

** Affects: xserver-xorg-input-synaptics (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug artful reproducible ubuntu

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

Title:
  Synaptics s3203 touchpad on Dell XPS12-9Q33 has no working buttons
  after recent upgrade

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-input-synaptics/+bug/1710862/+subscriptions

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

[Bug 1710862] Re: Synaptics s3203 touchpad on Dell XPS12-9Q33 has no working buttons after recent upgrade

2017-08-15 Thread emk2203
** Attachment added: "xmodmap-pp"
   
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-input-synaptics/+bug/1710862/+attachment/4932708/+files/xmodmap-pp

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

Title:
  Synaptics s3203 touchpad on Dell XPS12-9Q33 has no working buttons
  after recent upgrade

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-input-synaptics/+bug/1710862/+subscriptions

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


[Bug 1708922] Re: uvcvideo module does not work with Dell XPS 12 webcam

2017-08-14 Thread emk2203
Further information: ffmpeg stops after it detects broken frames, with
error messages like here:
https://superuser.com/questions/1048637/ffmpeg-video-recording-freezes-after-invalid-data-found-when-processing-input

[video4linux2,v4l2 @ 0xed0c353440] Dequeued v4l2 buffer contains 32533
bytes, but 614400 were expected. Flags: 0x00012001.
/dev/video0: Invalid data found when processing input
Finishing stream 0:0 without any data written to it.

ffmpeg behaviour is already in a 2 year old feature request which applies
here as well: https://trac.ffmpeg.org/ticket/4795

This confirms that the kernel uvcvideo driver is the source of the problem
- it delivers the broken frames to ffmpeg.

Kai-Heng Feng  schrieb am So., 13. Aug. 2017
um 17:25 Uhr:

> Okay, the error happens in avcodec_send_packet() or
> avcodec_receive_frame().
> Needs to find out what ffmpeg did here...
>
> ** Also affects: ffmpeg (Ubuntu)
>Importance: Undecided
>Status: New
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1708922
>
> Title:
>   uvcvideo module does not work with Dell XPS 12 webcam
>
> To manage notifications about this bug go to:
>
> https://bugs.launchpad.net/ubuntu/+source/ffmpeg/+bug/1708922/+subscriptions
>


** Bug watch added: FFmpeg Trac bug tracker #4795
   https://trac.ffmpeg.org/ticket/4795

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

Title:
  uvcvideo module does not work with Dell XPS 12 webcam

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

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


Re: [Bug 1708922] Re: uvcvideo module does not work with Dell XPS 12 webcam

2017-08-14 Thread emk2203
Here is my output from ffmpeg -f alsa -i default -f v4l2 -s 640x480 -i
/dev/video0 -acodec flac -vcodec libx264 output.mkv
ffmpeg version 3.3.3-1ubuntu1 Copyright (c) 2000-2017 the FFmpeg developers
  built with gcc 6.4.0 (Ubuntu 6.4.0-2ubuntu1) 20170724
  configuration: --prefix=/usr --extra-version=1ubuntu1
--toolchain=hardened --libdir=/usr/lib/x86_64-linux-gnu
--incdir=/usr/include/x86_64-linux-gnu --enable-gpl --disable-stripping
--enable-avresample --enable-avisynth --enable-gnutls --enable-ladspa
--enable-libass --enable-libbluray --enable-libbs2b --enable-libcaca
--enable-libcdio --enable-libflite --enable-libfontconfig
--enable-libfreetype --enable-libfribidi --enable-libgme --enable-libgsm
--enable-libmp3lame --enable-libopenjpeg --enable-libopenmpt
--enable-libopus --enable-libpulse --enable-librubberband --enable-libshine
--enable-libsnappy --enable-libsoxr --enable-libspeex --enable-libssh
--enable-libtheora --enable-libtwolame --enable-libvorbis --enable-libvpx
--enable-libwavpack --enable-libwebp --enable-libx265 --enable-libxvid
--enable-libzmq --enable-libzvbi --enable-omx --enable-openal
--enable-opengl --enable-sdl2 --enable-libdc1394 --enable-libiec61883
--enable-chromaprint --enable-frei0r --enable-libopencv --enable-libx264
--enable-shared
  libavutil  55. 58.100 / 55. 58.100
  libavcodec 57. 89.100 / 57. 89.100
  libavformat57. 71.100 / 57. 71.100
  libavdevice57.  6.100 / 57.  6.100
  libavfilter 6. 82.100 /  6. 82.100
  libavresample   3.  5.  0 /  3.  5.  0
  libswscale  4.  6.100 /  4.  6.100
  libswresample   2.  7.100 /  2.  7.100
  libpostproc54.  5.100 / 54.  5.100
Guessed Channel Layout for Input Stream #0.0 : stereo
Input #0, alsa, from 'default':
  Duration: N/A, start: 1502723857.171781, bitrate: 1536 kb/s
Stream #0:0: Audio: pcm_s16le, 48000 Hz, stereo, s16, 1536 kb/s
[video4linux2,v4l2 @ 0x3ddca87320] Dequeued v4l2 buffer contains 32756
bytes, but 614400 were expected. Flags: 0x00012001.
Input #1, video4linux2,v4l2, from '/dev/video0':
  Duration: N/A, bitrate: 147456 kb/s
Stream #1:0: Video: rawvideo (YUY2 / 0x32595559), yuyv422, 640x480,
147456 kb/s, 30 fps, 30 tbr, 1000k tbn, 1000k tbc
Stream mapping:
  Stream #1:0 -> #0:0 (rawvideo (native) -> h264 (libx264))
  Stream #0:0 -> #0:1 (pcm_s16le (native) -> flac (native))
Press [q] to stop, [?] for help
[video4linux2,v4l2 @ 0x3ddca87320] Dequeued v4l2 buffer contains 32534
bytes, but 614400 were expected. Flags: 0x00012001.
/dev/video0: Invalid data found when processing input
[alsa @ 0x3ddca6a520] Thread message queue blocking; consider raising the
thread_queue_size option (current value: 8)
frame=0 fps=0.0 q=0.0 size=   0kB time=-577014:32:22.77 bitrate=
-0.0kbframe=0 fps=0.0 q=0.0 size=   0kB time=-577014:32:22.77
bitrate=  -0.0kbframe=0 fps=0.0 q=0.0 size=   0kB
time=-577014:32:22.77 bitrate=  -0.0kbframe=0 fps=0.0 q=0.0 size=
 0kB time=-577014:32:22.77 bitrate=  -0.0kbframe=0 fps=0.0 q=0.0 size=
 0kB time=-577014:32:22.77 bitrate=  -0.0kbframe=0 fps=0.0 q=0.0
size=   0kB time=-577014:32:22.77 bitrate=  -0.0kbframe=0 fps=0.0
q=0.0 size=   0kB time=-577014:32:22.77 bitrate=  -0.0kbframe=0
fps=0.0 q=0.0 size=   0kB time=-577014:32:22.77 bitrate=  -0.0kbframe=
  0 fps=0.0 q=0.0 size=   0kB time=-577014:32:22.77 bitrate=
-0.0kbframe=0 fps=0.0 q=0.0 size=   0kB time=-577014:32:22.77
bitrate=  -0.0kbframe=0 fps=0.0 q=0.0 size=   0kB
time=-577014:32:22.77 bitrate=  -0.0kbframe=0 fps=0.0 q=0.0 size=
 0kB time=-577014:32:22.77 bitrate=  -0.0kbframe=0 fps=0.0 q=0.0 size=
 0kB time=-577014:32:22.77 bitrate=  -0.0kbframe=0 fps=0.0 q=0.0
size=   0kB time=-577014:32:22.77 bitrate=  -0.0kbframe=0 fps=0.0
q=0.0 size=   0kB time=-577014:32:22.77 bitrate=  -0.0kbframe=0
fps=0.0 q=0.0 size=   0kB time=-577014:32:22.77 bitrate=  -0.0kbframe=
  0 fps=0.0 q=0.0 size=   0kB time=-577014:32:22.77 bitrate=
-0.0kbframe=0 fps=0.0 q=0.0 size=   0kB time=-577014:32:22.77
bitrate=  -0.0kbframe=0 fps=0.0 q=0.0 size=   0kB
time=-577014:32:22.77 bitrate=  -0.0kbframe=0 fps=0.0 q=0.0 size=
 0kB time=-577014:32:22.77 bitrate=  -0.0kbframe=0 fps=0.0 q=0.0 size=
 0kB time=-577014:32:22.77 bitrate=  -0.0kbframe=0 fps=0.0 q=0.0
size=   0kB time=-577014:32:22.77 bitrate=  -0.0kbToo many packets
buffered for output stream 0:1.
Conversion failed!


Kai-Heng Feng  schrieb am So., 13. Aug. 2017
um 17:25 Uhr:

> Okay, the error happens in avcodec_send_packet() or
> avcodec_receive_frame().
> Needs to find out what ffmpeg did here...
>
> ** Also affects: ffmpeg (Ubuntu)
>Importance: Undecided
>Status: New
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1708922
>
> Title:
>   uvcvideo module does not work with Dell XPS 12 webcam
>
> To manage notifications 

Re: [Bug 1708922] Re: uvcvideo module does not work with Dell XPS 12 webcam

2017-08-12 Thread emk2203
I researched the issue some time ago. My webcam and several others like HP
are affected by a faulty driver for this webcam, which should be the kernel
uvcvideo module. This is the reason why it happens in several progs, like
guvcview and cheese.

vlc does it's own thing and does not rely on the kernel driver. This is the
reason why it's unaffected.

Am 12.08.2017 3:31 PM schrieb "Kai-Heng Feng"
:

> Nothing suspicious. Why do you think it's a kernel bug?
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1708922
>
> Title:
>   uvcvideo module does not work with Dell XPS 12 webcam
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/linux/+bug/
> 1708922/+subscriptions
>

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

Title:
  uvcvideo module does not work with Dell XPS 12 webcam

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

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


Re: [Bug 1708922] Re: uvcvideo module does not work with Dell XPS 12 webcam

2017-08-12 Thread emk2203
Here it is:

2017-08-11 8:19 GMT+02:00 Kai-Heng Feng :

> Can you attach dmesg?
>
> ** Information type changed from Private to Public
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1708922
>
> Title:
>   uvcvideo module does not work with Dell XPS 12 webcam
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/linux/+bug/
> 1708922/+subscriptions
>


** Attachment added: "dmesg.log"
   https://bugs.launchpad.net/bugs/1708922/+attachment/4931188/+files/dmesg.log

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

Title:
  uvcvideo module does not work with Dell XPS 12 webcam

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

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


[Bug 1660984] [NEW] anki doesn't start on zesty (missing dependencies)

2017-02-01 Thread emk2203
Public bug reported:

anki doesn't start. If started from the CLI, the following errors show:

Traceback (most recent call last):
  File "/usr/bin/anki", line 7, in 
import aqt
  File "/usr/share/anki/aqt/__init__.py", line 12, in 
from aqt.qt import *
  File "/usr/share/anki/aqt/qt.py", line 22, in 
from PyQt4.QtWebKit import QWebPage, QWebView, QWebSettings
ImportError: No module named QtWebKit

** Affects: anki (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/1660984

Title:
  anki doesn't start on zesty (missing dependencies)

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

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


Re: [Bug 1642901] Re: ffmpeg dependent on libSDL-1.2.so.0 instead libsdl2-2.0-0

2016-11-19 Thread emk2203
Thanks for taking the time to explain. I had an older backup restored,
which brought an obsolete ffmpeg version into ~/bin. This gave the false
alarm, because ~/bin had priority in my PATH. Sorry for causing unnecessary
work.

Erik

Andreas Cadhalpun  schrieb am Sa., 19. Nov.
2016 um 00:27 Uhr:

> I've just verified that ffmpeg 3.2-2 from zesty starts fine after
> installation in a minimal chroot.
> Your problem is caused by third-party libraries.
> To identify the problematic one, try running the following command:
> $ for lib in $(ldd /usr/bin/ffmpeg | sed 's/.*=> \(.*\) (.*/\1/'); do [ -e
> "$lib" ] && ldd "$lib" | grep libSDL && echo "$lib"; done
> libSDL2-2.0.so.0 => /usr/lib/x86_64-linux-gnu/libSDL2-2.0.so.0
> (0x7f2c0db1e000)
> /usr/lib/x86_64-linux-gnu/libavdevice.so.57
>
> As you can see, there is no libSDL1.2 here thus I'm closing this bug as
> invalid.
>
> ** Changed in: ffmpeg (Ubuntu)
>Status: New => Invalid
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1642901
>
> Title:
>   ffmpeg dependent on libSDL-1.2.so.0 instead libsdl2-2.0-0
>
> To manage notifications about this bug go to:
>
> https://bugs.launchpad.net/ubuntu/+source/ffmpeg/+bug/1642901/+subscriptions
>

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

Title:
  ffmpeg dependent on libSDL-1.2.so.0 instead libsdl2-2.0-0

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

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


[Bug 1642901] [NEW] ffmpeg dependent on libSDL-1.2.so.0 instead libsdl2-2.0-0

2016-11-18 Thread emk2203
Public bug reported:

ffmpeg from zesty universe (7:3.2-2) is supposed to depend on
libsdl2-2.0-0, but after installing, error "ffmpeg: error while loading
shared libraries: libSDL-1.2.so.0: cannot open shared object file: No
such file or directory" after running it

** Affects: ffmpeg (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/1642901

Title:
  ffmpeg dependent on libSDL-1.2.so.0 instead libsdl2-2.0-0

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

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


[Bug 1611124] Re: W: Possible missing firmware /lib/firmware/i915/kbl_guc_ver9_14.bin for module i915

2016-09-29 Thread emk2203
Please re-open. 4.8 is now the official Yakkety kernel, running 4.8.0-17
and encountering this bug.

i915 crashes often, significantly affecting the machine.

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

Title:
  W: Possible missing firmware /lib/firmware/i915/kbl_guc_ver9_14.bin
  for module i915

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

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


[Bug 1590928] [NEW] package xrdp 0.9.0~20160601+git703fedd-2 failed to install/upgrade: Unterprozess installiertes post-installation-Skript gab den Fehlerwert 1 zurück

2016-06-09 Thread emk2203
Public bug reported:

during a apt update && apt full-upgrade operation; a apt purge xrdp,
followed by apt install xrdp, rectified the situation

ProblemType: Package
DistroRelease: Ubuntu 16.10
Package: xrdp 0.9.0~20160601+git703fedd-2
ProcVersionSignature: Ubuntu 4.4.0-23.41-generic 4.4.10
Uname: Linux 4.4.0-23-generic x86_64
ApportVersion: 2.20.1-0ubuntu4
Architecture: amd64
Date: Thu Jun  9 20:57:46 2016
ErrorMessage: Unterprozess installiertes post-installation-Skript gab den 
Fehlerwert 1 zurück
InstallationDate: Installed on 2014-09-14 (634 days ago)
InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Alpha amd64 (20140914)
RelatedPackageVersions:
 dpkg 1.18.7ubuntu1
 apt  1.3~exp1
SourcePackage: xrdp
Title: package xrdp 0.9.0~20160601+git703fedd-2 failed to install/upgrade: 
Unterprozess installiertes post-installation-Skript gab den Fehlerwert 1 zurück
UpgradeStatus: No upgrade log present (probably fresh install)
modified.conffile..etc.pam.d.sesman: [deleted]
modified.conffile..etc.pam.d.xrdp-sesman: [deleted]

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


** Tags: amd64 apport-package third-party-packages yakkety

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

Title:
  package xrdp 0.9.0~20160601+git703fedd-2 failed to install/upgrade:
  Unterprozess installiertes post-installation-Skript gab den Fehlerwert
  1 zurück

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

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

[Bug 1581804] [NEW] v4l2loopback-dkms 0.9.1-4: v4l2loopback kernel module failed to build

2016-05-14 Thread emk2203
Public bug reported:

DKMS make.log for v4l2loopback-0.9.1 for kernel 4.4.0-22-generic (x86_64)
Sa 14. Mai 14:24:14 CEST 2016
Building v4l2-loopback driver...
make -C /lib/modules/4.4.0-22-generic/build 
M=/var/lib/dkms/v4l2loopback/0.9.1/build modules
make[1]: Verzeichnis „/usr/src/linux-headers-4.4.0-22-generic“ wird betreten
arch/x86/Makefile:133: stack-protector enabled but compiler support broken
Makefile:670: Cannot use CONFIG_CC_STACKPROTECTOR_STRONG: 
-fstack-protector-strong not supported by compiler
  CC [M]  /var/lib/dkms/v4l2loopback/0.9.1/build/v4l2loopback.o
/var/lib/dkms/v4l2loopback/0.9.1/build/v4l2loopback.c:1:0: error: code model 
kernel does not support PIC mode
 /* -*- c-file-style: "linux" -*- */
 ^
scripts/Makefile.build:264: die Regel für Ziel 
„/var/lib/dkms/v4l2loopback/0.9.1/build/v4l2loopback.o“ scheiterte
make[2]: *** [/var/lib/dkms/v4l2loopback/0.9.1/build/v4l2loopback.o] Fehler 1
Makefile:1396: die Regel für Ziel 
„_module_/var/lib/dkms/v4l2loopback/0.9.1/build“ scheiterte
make[1]: *** [_module_/var/lib/dkms/v4l2loopback/0.9.1/build] Fehler 2
make[1]: Verzeichnis „/usr/src/linux-headers-4.4.0-22-generic“ wird verlassen
Makefile:42: die Regel für Ziel „v4l2loopback.ko“ scheiterte
make: *** [v4l2loopback.ko] Fehler 2

ProblemType: Package
DistroRelease: Ubuntu 16.10
Package: v4l2loopback-dkms 0.9.1-4
ProcVersionSignature: Ubuntu 4.4.0-22.39-generic 4.4.8
Uname: Linux 4.4.0-22-generic x86_64
ApportVersion: 2.20.1-0ubuntu3
Architecture: amd64
DKMSKernelVersion: 4.4.0-22-generic
Date: Sat May 14 14:24:18 2016
DuplicateSignature: 
dkms:v4l2loopback-dkms:0.9.1-4:/var/lib/dkms/v4l2loopback/0.9.1/build/v4l2loopback.c:1:0:
 error: code model kernel does not support PIC mode
InstallationDate: Installed on 2014-09-14 (607 days ago)
InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Alpha amd64 (20140914)
PackageArchitecture: all
PackageVersion: 0.9.1-4
RelatedPackageVersions:
 dpkg 1.18.4ubuntu2
 apt  1.2.12
SourcePackage: v4l2loopback
Title: v4l2loopback-dkms 0.9.1-4: v4l2loopback kernel module failed to build
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: v4l2loopback (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/1581804

Title:
  v4l2loopback-dkms 0.9.1-4: v4l2loopback kernel module failed to build

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

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

[Bug 1464990] Re: Job for dnsmasq.service failed because the control process exited with error code

2016-05-12 Thread emk2203
This maybe a duplicate of #1531184
https://bugs.launchpad.net/ubuntu/+source/dnsmasq/+bug/1531184 .

The proposed fix of adding the following to the [Unit] section of
dnsmasq.service fixes the problem:

 After=network-online.target
 Wants=network-online.target

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

Title:
  Job for dnsmasq.service failed because the control process exited with
  error code

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

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


[Bug 1464990] Re: Job for dnsmasq.service failed because the control process exited with error code

2016-05-12 Thread emk2203
>Does it cause a noticeable malfunction?

Yes. I run Ubuntu 16.04 on an ARM system, and the bug makes it
impossible to install pi hole https://pi-hole.net/ on it, an ad blocker
for other devices in the network. The effect of the bug is that other
devices can't connect to the internet via this system, because dnsmasq
is not running.

** Changed in: dnsmasq (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/1464990

Title:
  Job for dnsmasq.service failed because the control process exited with
  error code

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

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


[Bug 1286596] Re: mediascanner-service-2.0 crashed with SIGABRT in __gnu_cxx::__verbose_terminate_handler()

2016-05-10 Thread emk2203
Bug is still present in Yakkety.

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

Title:
  mediascanner-service-2.0 crashed with SIGABRT in
  __gnu_cxx::__verbose_terminate_handler()

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

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


[Bug 1262719] Re: Crash if trying to compress contents of a directory mounted in nautilus via sftp

2016-04-24 Thread emk2203
Also affects mounted samba shares. Whatever is not mounted locally
crashes fileroller when trying to add files to an archive or compress.

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

Title:
  Crash if trying to compress contents of a directory mounted in
  nautilus via sftp

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/file-roller/+bug/1262719/+subscriptions

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


[Bug 1470862] Re: When using fglrx module, the virtual consoles are blank and useless

2016-04-13 Thread emk2203
Don't know if it makes sense to post, but I have the same bug
**without** fglrx, with NVIDIA hardware on a freshly installed Xenial
Xerus beta 2. It was there from the start. Maybe this helps finding the
root cause. It's not just fglrx.

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

Title:
  When using fglrx module, the virtual consoles are blank and useless

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/fglrx-installer/+bug/1470862/+subscriptions

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


[Bug 1569335] [NEW] glances doesn't show sensor information - hddtemp, lmsensors installed

2016-04-12 Thread emk2203
Public bug reported:

glances doesn't show the sensor information after a standard
installation. lm-sensors and hddtemp are installed, (recommended by
glances), but some python glue seems to be missing.

Author suggests py3sensors on github, but it is nowhere to be found on
Ubuntu 16.04.

** Affects: glances (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/1569335

Title:
  glances doesn't show sensor information - hddtemp, lmsensors installed

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

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


[Bug 1286596] Re: mediascanner-service-2.0 crashed with SIGABRT in __gnu_cxx::__verbose_terminate_handler()

2016-04-05 Thread emk2203
Bug is still present in Xenial.

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

Title:
  mediascanner-service-2.0 crashed with SIGABRT in
  __gnu_cxx::__verbose_terminate_handler()

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

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


[Bug 1485254] [NEW] package dbus 1.8.12-1ubuntu5 failed to install/upgrade: Abhängigkeitsprobleme - Trigger bleiben unverarbeitet

2015-08-15 Thread emk2203
Public bug reported:

during apt-get dist-upgrade

ProblemType: Package
DistroRelease: Ubuntu 15.10
Package: dbus 1.8.12-1ubuntu5
ProcVersionSignature: Ubuntu 4.1.0-3.3-generic 4.1.3
Uname: Linux 4.1.0-3-generic x86_64
ApportVersion: 2.18-0ubuntu6
Architecture: amd64
Date: Sat Aug 15 23:00:47 2015
DuplicateSignature: package:dbus:1.8.12-1ubuntu5:Abhängigkeitsprobleme - 
Trigger bleiben unverarbeitet
ErrorMessage: Abhängigkeitsprobleme - Trigger bleiben unverarbeitet
InstallationDate: Installed on 2014-09-14 (335 days ago)
InstallationMedia: Ubuntu 14.10 Utopic Unicorn - Alpha amd64 (20140914)
RelatedPackageVersions:
 dpkg 1.18.2ubuntu1
 apt  1.0.9.10ubuntu1
SourcePackage: dbus
Title: package dbus 1.8.12-1ubuntu5 failed to install/upgrade: 
Abhängigkeitsprobleme - Trigger bleiben unverarbeitet
UpgradeStatus: Upgraded to wily on 2015-06-26 (49 days ago)

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


** Tags: amd64 apport-package wily

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

Title:
  package dbus 1.8.12-1ubuntu5 failed to install/upgrade:
  Abhängigkeitsprobleme - Trigger bleiben unverarbeitet

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

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

[Bug 1413694] Re: Since 3.18.x, iwlwifi has severe connection problems

2015-01-31 Thread emk2203
Bug still present in 3.18.0-12

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

Title:
  Since 3.18.x, iwlwifi has severe connection problems

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

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


[Bug 1413694] Re: Since 3.18.x, iwlwifi has severe connection problems

2015-01-28 Thread emk2203
[  934.033045] iwlwifi :06:00.0: fail to flush all tx fifo queues Q 0
[  934.033050] iwlwifi :06:00.0: Current SW read_ptr 74 write_ptr 77


[  934.033213] iwl data: : 00 1c 00 00 00 00 00 00 00 00 00 00 00 00 00 
00  

[  934.033225] iwlwifi :06:00.0: FH TRBs(0) = 0x
[  934.033237] iwlwifi :06:00.0: FH TRBs(1) = 0xc011008e


[  934.033249] iwlwifi :06:00.0: FH TRBs(2) = 0x


[  934.033261] iwlwifi :06:00.0: FH TRBs(3) = 0x8030004c


[  934.033273] iwlwifi :06:00.0: FH TRBs(4) = 0x


[  934.033285] iwlwifi :06:00.0: FH TRBs(5) = 0x


[  934.033296] iwlwifi :06:00.0: FH TRBs(6) = 0x


[  934.033308] iwlwifi :06:00.0: FH TRBs(7) = 0x00709082


[  934.033358] iwlwifi :06:00.0: Q 0 is active and mapped to fifo 3 ra_tid 
0x [74,77]  
 
[  934.033408] iwlwifi :06:00.0: Q 1 is active and mapped to fifo 2 ra_tid 
0x [0,0]
 
[  934.033457] iwlwifi :06:00.0: Q 2 is active and mapped to fifo 1 ra_tid 
0x [39,39]  
 
[  934.033506] iwlwifi :06:00.0: Q 3 is active and mapped to fifo 0 ra_tid 
0x [0,0]
 
[  934.033556] iwlwifi :06:00.0: Q 4 is inactive and mapped to fifo 0 
ra_tid 0x [0,0] 
  
[  934.033605] iwlwifi :06:00.0: Q 5 is inactive and mapped to fifo 0 
ra_tid 0x [0,0] 
  
[  934.033654] iwlwifi :06:00.0: Q 6 is inactive and mapped to fifo 0 
ra_tid 0x [0,0] 
  
[  934.033703] iwlwifi :06:00.0: Q 7 is inactive and mapped to fifo 0 
ra_tid 0x [0,0] 
  
[  934.033753] iwlwifi :06:00.0: Q 8 is inactive and mapped to fifo 0 
ra_tid 0x [0,0] 
  
[  934.033802] iwlwifi :06:00.0: Q 9 is active and mapped to fifo 7 ra_tid 
0x [131,131]
 
[  934.033851] iwlwifi :06:00.0: Q 10 is inactive and mapped to fifo 0 
ra_tid 0x [0,0] 
 
[  934.033900] iwlwifi :06:00.0: Q 11 is inactive and mapped to fifo 0 
ra_tid 0x [0,0] 
 
[  934.033950] iwlwifi :06:00.0: Q 12 is inactive and mapped to fifo 0 
ra_tid 0x [0,0] 
 
[  934.033999] iwlwifi :06:00.0: Q 13 is inactive and mapped to fifo 0 
ra_tid 0x [0,0] 
 
[  

[Bug 1413694] Re: Since 3.18.x, iwlwifi has severe connection problems

2015-01-28 Thread emk2203
[  934.033045] iwlwifi :06:00.0: fail to flush all tx fifo queues Q 0
[  934.033050] iwlwifi :06:00.0: Current SW read_ptr 74 write_ptr 77


[  934.033213] iwl data: : 00 1c 00 00 00 00 00 00 00 00 00 00 00 00 00 
00  

[  934.033225] iwlwifi :06:00.0: FH TRBs(0) = 0x
[  934.033237] iwlwifi :06:00.0: FH TRBs(1) = 0xc011008e


[  934.033249] iwlwifi :06:00.0: FH TRBs(2) = 0x


[  934.033261] iwlwifi :06:00.0: FH TRBs(3) = 0x8030004c


[  934.033273] iwlwifi :06:00.0: FH TRBs(4) = 0x


[  934.033285] iwlwifi :06:00.0: FH TRBs(5) = 0x


[  934.033296] iwlwifi :06:00.0: FH TRBs(6) = 0x


[  934.033308] iwlwifi :06:00.0: FH TRBs(7) = 0x00709082


[  934.033358] iwlwifi :06:00.0: Q 0 is active and mapped to fifo 3 ra_tid 
0x [74,77]  
 
[  934.033408] iwlwifi :06:00.0: Q 1 is active and mapped to fifo 2 ra_tid 
0x [0,0]
 
[  934.033457] iwlwifi :06:00.0: Q 2 is active and mapped to fifo 1 ra_tid 
0x [39,39]  
 
[  934.033506] iwlwifi :06:00.0: Q 3 is active and mapped to fifo 0 ra_tid 
0x [0,0]
 
[  934.033556] iwlwifi :06:00.0: Q 4 is inactive and mapped to fifo 0 
ra_tid 0x [0,0] 
  
[  934.033605] iwlwifi :06:00.0: Q 5 is inactive and mapped to fifo 0 
ra_tid 0x [0,0] 
  
[  934.033654] iwlwifi :06:00.0: Q 6 is inactive and mapped to fifo 0 
ra_tid 0x [0,0] 
  
[  934.033703] iwlwifi :06:00.0: Q 7 is inactive and mapped to fifo 0 
ra_tid 0x [0,0] 
  
[  934.033753] iwlwifi :06:00.0: Q 8 is inactive and mapped to fifo 0 
ra_tid 0x [0,0] 
  
[  934.033802] iwlwifi :06:00.0: Q 9 is active and mapped to fifo 7 ra_tid 
0x [131,131]
 
[  934.033851] iwlwifi :06:00.0: Q 10 is inactive and mapped to fifo 0 
ra_tid 0x [0,0] 
 
[  934.033900] iwlwifi :06:00.0: Q 11 is inactive and mapped to fifo 0 
ra_tid 0x [0,0] 
 
[  934.033950] iwlwifi :06:00.0: Q 12 is inactive and mapped to fifo 0 
ra_tid 0x [0,0] 
 
[  934.033999] iwlwifi :06:00.0: Q 13 is inactive and mapped to fifo 0 
ra_tid 0x [0,0] 
 
[  

[Bug 1413694] Re: Since 3.18.x, iwlwifi has severe connection problems

2015-01-28 Thread emk2203
This BIOS update came out literally one hour after I reported the bug, I
updated on the same day with no effect on the bug.

As you see: 
root@XPS12-9Q33:~# dmidecode -s bios-version  dmidecode -s bios-release-date
A07
11/17/2014

The bug stays the same - after a grace period of a few minutes up to an
hour or so, the connection drops, subsequent connection attempts are met
with failure as outlined in the original report and documented by dmesg
log.



** 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/1413694

Title:
  Since 3.18.x, iwlwifi has severe connection problems

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

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


  1   2   >