[Desktop-packages] [Bug 1771880] Re: Seahorse unable to import pkcs12 certificates

2022-11-04 Thread Matej Kovacic 
This is a real shame. I am using Ubuntu 22.10 with Seahorse 42, and the
problem still persists. The bug is several years old and there is no
solution yet.

The world is going paperless, people want to use their Linux systems for
serious work and business, but certificate management is not supported.

Just a short question - is this issue not important? You think adding
some new features in a form of new shiny icons is more important than
ability to digitally sign documents in 21th century? (Yes, I am actually
asking that question).

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-keyring in Ubuntu.
https://bugs.launchpad.net/bugs/1771880

Title:
  Seahorse unable to import pkcs12 certificates

Status in seahorse:
  New
Status in gnome-keyring package in Ubuntu:
  Triaged
Status in seahorse package in Ubuntu:
  Triaged
Status in gnome-keyring package in Fedora:
  New
Status in seahorse package in Fedora:
  Unknown

Bug description:
  seahorse 3.20.0-5 / gnome-keyring 3.28.0.2-1ubuntu1.18.04.1 / Ubuntu
  18.04 LTS / GNOME 3.28.1

  When trying to import a certificate into seahorse/gnome-keyring on
  Ubuntu 18.04, seahorse GUI application shows the 'import' button
  greyed out, while mouse hovering the "import" button shows the message
  "Cannot import because there are no compatible importers".

  This problem doesn't occur on Ubuntu 16.04 LTS (Seahorse 3.18.0), as
  I've just tested on my wife's laptop, but happens in my Laptop with
  Ubuntu 18.04 LTS (Seahorse 3.20.0-5).

  Because that problem, it's not possible to digitally sign documents
  with LibreOffice.

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


-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1950040] Re: Wayland Screensharing broken in Ubuntu 21.10

2022-11-03 Thread Matej Kovacic 
Weel, the bug may be closed, but it is not gone. I have Ubuntu 22.10
with Firefox 106.0 (Mozilla Firefox Snap for Ubuntu / canonical-002 -
1.0) and when I open https://www.webrtc-experiment.com/Pluginfree-
Screen-Sharing/ and try to share one window - Firefox just crashes.

I installed pipewire-media-session package, but of course it doesn't
help.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xdg-desktop-portal-gtk in Ubuntu.
https://bugs.launchpad.net/bugs/1950040

Title:
  Wayland Screensharing broken in Ubuntu 21.10

Status in chromium-browser package in Ubuntu:
  Invalid
Status in firefox package in Ubuntu:
  Fix Released
Status in gnome-shell package in Ubuntu:
  Invalid
Status in pipewire package in Ubuntu:
  Invalid
Status in xdg-desktop-portal package in Ubuntu:
  Invalid
Status in xdg-desktop-portal-gtk package in Ubuntu:
  Fix Released

Bug description:
  Freshly installed Ubuntu 21.10, screen sharing does not work with any
  browser, tested the following options:

  - Firefox snap
  - Firefox deb
  - Chromium snap
  - Chromium flatpak

  Steps to reproduce:

  1. Go to 
https://www.webrtc-experiment.com/Pluginfree-Screen-Sharing/#7325517390736006
  2. Select to share the whole desktop in the xdg-desktop-portal
  3. Notice the orange screen share indicator in Gnome-Shell but actually 
nothing is shared in the browser.

  This should be handled high priority since this is a critical feature
  during the pandemic.

  Filed against ubuntu-meta since I don't know exactly which package to
  blame, whether it's pipewire, xdg-desktop portal or some problem
  directely with mutter / gnome-shell, please reassign accordingly.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1950040/+subscriptions


-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1406031] Re: Cannot connect to wifi having short password

2021-08-03 Thread Matej Kovacic 
Sorry, this is just sick.

Bug reported and confirmed (!) in 2016, but still not resolved.

I confirm this bug still exists and is affecting me and other users. We
do not have control over WiFi, so we cannot change the password. But we
cannot use the WiFi, because of this bug.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1406031

Title:
  Cannot connect to wifi having short password

Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  I can't connect to a wifi network with security "WPA & WPA2 Personal"
  and a password of 7 ASCII characters. Of course this password is
  invalid, but I can't change that, and I should be able to connect
  anyway. Actually I could connect the first time, and after that it
  wouldn't enable the "connect" button anymore. I hope we're not in the
  business of policing other people's wifi... I really can't configure
  their system, but if you relax the constraints on your side, then I
  can have wifi access and work on my PhD project. Thanks for
  considering the net value of policing other people.

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


-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1883174] Re: Some (or all) desktop icons are missing

2021-06-05 Thread Matej Kovacic 
Here we have a great example how bugs are being solved.

Since there was no good solution, I updated 20.04 to 20.10. Bug was
still there. Then I updated to 21.04 - and, voila, bug is not present
anymore.

So the solution is clear. Just wait till bugs dissapear by "natural
reasons"... or till users switch to some other operating system.

Great way to go, really.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-shell-extension-desktop-icons in
Ubuntu.
https://bugs.launchpad.net/bugs/1883174

Title:
  Some (or all) desktop icons are missing

Status in gnome-shell-extension-desktop-icons:
  Unknown
Status in gnome-shell-extension-desktop-icons package in Ubuntu:
  In Progress

Bug description:
  OS: Ubuntu 20.04
  GNOME: 3.36.2
  Extension: 3.36.2

  Sometimes, some icons in my Desktop folder just don't appear on the
  desktop. The missing icons aren't invisible, it's like they're not in
  the folder. Clicking on the empty space where they should be does
  nothing. Mousing over the empty space does nothing. See attached
  screenshot. As you can see, there are many missing.

  Not consistently reproducible, but frequent.

  This isn't great info, I know. Let me know what else I can provide.

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

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1883174] Re: Some (or all) desktop icons are missing

2021-06-03 Thread Matej Kovacic 
Oh, of course not. This is not a solution. At all.

There is dependency of gnome-shell-extension-desktop-icons to ubuntu-
desktop. Just perfect.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-shell-extension-desktop-icons in
Ubuntu.
https://bugs.launchpad.net/bugs/1883174

Title:
  Some (or all) desktop icons are missing

Status in gnome-shell-extension-desktop-icons:
  Unknown
Status in gnome-shell-extension-desktop-icons package in Ubuntu:
  In Progress

Bug description:
  OS: Ubuntu 20.04
  GNOME: 3.36.2
  Extension: 3.36.2

  Sometimes, some icons in my Desktop folder just don't appear on the
  desktop. The missing icons aren't invisible, it's like they're not in
  the folder. Clicking on the empty space where they should be does
  nothing. Mousing over the empty space does nothing. See attached
  screenshot. As you can see, there are many missing.

  Not consistently reproducible, but frequent.

  This isn't great info, I know. Let me know what else I can provide.

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

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1883174] Re: Some (or all) desktop icons are missing

2021-06-03 Thread Matej Kovacic 
This bug also affects me. I just can't believe what an ignorance from
the maintainers to not resolve this issue already.

Do we have a working solution yet or not?

Some report that "sudo apt remove gnome-shell-extension-desktop-icons"
solves the problem, but others that this causes even more problems.

Can you advise me, because I do not want to have additional problems.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-shell-extension-desktop-icons in
Ubuntu.
https://bugs.launchpad.net/bugs/1883174

Title:
  Some (or all) desktop icons are missing

Status in gnome-shell-extension-desktop-icons:
  Unknown
Status in gnome-shell-extension-desktop-icons package in Ubuntu:
  In Progress

Bug description:
  OS: Ubuntu 20.04
  GNOME: 3.36.2
  Extension: 3.36.2

  Sometimes, some icons in my Desktop folder just don't appear on the
  desktop. The missing icons aren't invisible, it's like they're not in
  the folder. Clicking on the empty space where they should be does
  nothing. Mousing over the empty space does nothing. See attached
  screenshot. As you can see, there are many missing.

  Not consistently reproducible, but frequent.

  This isn't great info, I know. Let me know what else I can provide.

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

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 875676] Re: Backing up fails with 'IOError CRC check failed'.

2021-02-27 Thread Matej Kovacic 
Wow, this is so interesting. Almost 10 years old bug, official (!)
Ubuntu app for backup, and not fixed yet.

Guys, seriously. I highly recommend BordBackup. It is reliable, fast,
has an active development (!) and GUI frontend. And yes, it is working
on different OS'es.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to duplicity in Ubuntu.
https://bugs.launchpad.net/bugs/875676

Title:
  Backing up fails with 'IOError CRC check failed'.

Status in Duplicity:
  Confirmed
Status in duplicity package in Ubuntu:
  Confirmed

Bug description:
  For 4 days déjà dup hasn't been able to perform a backup. It fails
  with the error

  Failed to read /tmp/duplicity-lJcUDl-tempdir/mktemp-o4LYSJ-1: (, IOError('CRC check failed 0x8434f7d2L !=
  0x3d503338L',), )

  There is another similar bug #676767 where deleting ~/.cache/deja-dup
  helps. In this case it doesn't.

  I'm quite certain that my backup drive isn't corrupted. (It's a
  raid5.) I'd be happy to provide any additional information needed.

  --

  System information:
  Ubuntu 11.10
  deja-dup 20.0-0ubuntu3
  duplicity 0.6.15-0ubuntu2

  Logs:
  deja-dup.log: http://pastie.org/2705320
  deja-dup.gsettings: http://pastie.org/2705322

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

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

Re: [Desktop-packages] [Bug 1906642] Re: Xorg crashes with abort in iris_dri.so

2020-12-08 Thread Matej Malčić 
Thank you for your effort, i am sorry i did not respond to you. Was working
on project with deadline. I return my pc to the store, they should fix it.

Thank you once again, great regards

uto, 8. pro 2020. 07:11 Daniel van Vugt <1906...@bugs.launchpad.net> je
napisao:

> The only other similar crash I can find is bug 1871959.
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1906642
>
> Title:
>   Xorg crashes with abort in iris_dri.so
>
> Status in mesa package in Ubuntu:
>   Incomplete
> Status in xorg-server package in Ubuntu:
>   Incomplete
>
> Bug description:
>   System is crashing, logging out and i am constantly losing all my work
>   if it's not saved
>
>   Description:  Ubuntu 20.04 LTS (fossa-beric-icl X31)
>   Release:  20.04
>
>   N: Unable to locate package pkgname
>
>   I expect not to happen (crash->log out)
>
>   Instead, it happened
>
>   ProblemType: Bug
>   DistroRelease: Ubuntu 20.04
>   Package: xorg 1:7.7+19ubuntu14
>   ProcVersionSignature: Ubuntu 5.6.0-1033.35-oem 5.6.19
>   Uname: Linux 5.6.0-1033-oem x86_64
>   ApportVersion: 2.20.11-0ubuntu27.12
>   Architecture: amd64
>   BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
>   CasperMD5CheckResult: skip
>   CompositorRunning: None
>   CurrentDesktop: ubuntu:GNOME
>   Date: Thu Dec  3 12:33:11 2020
>   DistUpgraded: Fresh install
>   DistributionChannelDescriptor:
># This is the distribution channel descriptor for the OEM CDs
># For more information see
> http://wiki.ubuntu.com/DistributionChannelDescriptor
>canonical-oem-somerville-focal-amd64-20200502-85
>   DistroCodename: focal
>   DistroVariant: ubuntu
>   ExtraDebuggingInterest: Yes, including running git bisection searches
>   GraphicsCard:
>Intel Corporation Device [8086:8a56] (rev 07) (prog-if 00 [VGA
> controller])
>  Subsystem: Dell Device [1028:0a2a]
>   InstallationDate: Installed on 2020-09-19 (74 days ago)
>   InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary
> 20200502-05:58
>   MachineType: Dell Inc. Vostro 3501
>   ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.6.0-1033-oem
> root=UUID=6b577a12-8585-4836-a5fc-abc3857f42ce ro quiet splash vt.handoff=7
>   SourcePackage: xorg
>   Symptom: display
>   Title: Xorg crash
>   UpgradeStatus: No upgrade log present (probably fresh install)
>   dmi.bios.date: 07/06/2020
>   dmi.bios.vendor: Dell Inc.
>   dmi.bios.version: 1.0.0
>   dmi.board.name: 01D26F
>   dmi.board.vendor: Dell Inc.
>   dmi.board.version: A00
>   dmi.chassis.type: 10
>   dmi.chassis.vendor: Dell Inc.
>   dmi.modalias:
> dmi:bvnDellInc.:bvr1.0.0:bd07/06/2020:svnDellInc.:pnVostro3501:pvr:rvnDellInc.:rn01D26F:rvrA00:cvnDellInc.:ct10:cvr:
>   dmi.product.family: Vostro
>   dmi.product.name: Vostro 3501
>   dmi.product.sku: 0A2A
>   dmi.sys.vendor: Dell Inc.
>   version.compiz: compiz N/A
>   version.libdrm2: libdrm2 2.4.101-2
>   version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1
>   version.libgl1-mesa-glx: libgl1-mesa-glx N/A
>   version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.6
>   version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
>   version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
>   version.xserver-xorg-video-intel: xserver-xorg-video-intel
> 2:2.99.917+git20200226-1
>   version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1906642/+subscriptions
>

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg-server in Ubuntu.
https://bugs.launchpad.net/bugs/1906642

Title:
  Xorg crashes with abort in iris_dri.so

Status in mesa package in Ubuntu:
  Incomplete
Status in xorg-server package in Ubuntu:
  Incomplete

Bug description:
  System is crashing, logging out and i am constantly losing all my work
  if it's not saved

  Description:  Ubuntu 20.04 LTS (fossa-beric-icl X31)
  Release:  20.04

  N: Unable to locate package pkgname

  I expect not to happen (crash->log out)

  Instead, it happened

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.6.0-1033.35-oem 5.6.19
  Uname: Linux 5.6.0-1033-oem x86_64
  ApportVersion: 2.20.11-0ubuntu27.12
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Dec  3 12:33:11 2020
  DistUpgraded: Fresh install
  DistributionChannelDescriptor:
   # This is the distribution channel descriptor for the OEM CDs
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-focal-amd64-20200502-85
  DistroCodename: focal
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, including running git bisection searches

[Desktop-packages] [Bug 1771880] Re: Seahorse unable to import pkcs12 certificates

2020-07-31 Thread Matej Kovacic 
This is really amazing. I still have the same problem.

And yes, it is NOT triaged.

I have Ubuntu 18.04.4 LTS. LibreOffice is version 6.0.7.3.

I would expect some things just work in 21tg century. But obviously, I
am wrong.

Maybe the problem is, that Ubuntu developers does not use encryption and
digital signatures? C'mon people, we are in 2020. How do you expect that
business will not use such things?

Or maybe Ubuntu is targeted for home playing only?

I have a very simple question: I am using Ubuntu version, which is still
officially supported. What should I do that I will be able to sign
LibreOffice documents and PDF's?

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-keyring in Ubuntu.
https://bugs.launchpad.net/bugs/1771880

Title:
  Seahorse unable to import pkcs12 certificates

Status in seahorse:
  New
Status in gnome-keyring package in Ubuntu:
  Confirmed
Status in seahorse package in Ubuntu:
  Triaged
Status in gnome-keyring package in Fedora:
  New
Status in seahorse package in Fedora:
  Unknown

Bug description:
  seahorse 3.20.0-5 / gnome-keyring 3.28.0.2-1ubuntu1.18.04.1 / Ubuntu
  18.04 LTS / GNOME 3.28.1

  When trying to import a certificate into seahorse/gnome-keyring on
  Ubuntu 18.04, seahorse GUI application shows the 'import' button
  greyed out, while mouse hovering the "import" button shows the message
  "Cannot import because there are no compatible importers".

  This problem doesn't occur on Ubuntu 16.04 LTS (Seahorse 3.18.0), as
  I've just tested on my wife's laptop, but happens in my Laptop with
  Ubuntu 18.04 LTS (Seahorse 3.20.0-5).

  Because that problem, it's not possible to digitally sign documents
  with LibreOffice.

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

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 604635]

2019-03-13 Thread Matej 
(In reply to Justin Lebar (not reading bugmail) from comment #151)
> The release notes are wrong.  The API exists, but it's not implemented in
> desktop Firefox.

And would it be possible to link to the description of this API? Is it
documented somewhere on MDN? I am interested in the implementation on
FxOS/FxAndroid so lack of implementation on Desktop doesn’t bother me.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-power-manager in Ubuntu.
https://bugs.launchpad.net/bugs/604635

Title:
  Have default settings be energy star 5.0 compliant

Status in Chromium Browser:
  Unknown
Status in Mozilla Firefox:
  Fix Released
Status in gnome-power:
  Won't Fix
Status in OEM Priority Project:
  Fix Released
Status in chromium-browser package in Ubuntu:
  Triaged
Status in firefox package in Ubuntu:
  Triaged
Status in gnome-power-manager package in Ubuntu:
  Fix Released
Status in rhythmbox package in Ubuntu:
  Fix Released

Bug description:
  Binary package hint: gnome-power-manager

  Energy star is a standard backed by the US government to set standards for 
energy use of devices.
  The specification for Operating System settings can be found here:
  http://www.energystar.gov/index.cfm?c=revisions.computer_spec

  Spec direct link (page 13):
  
http://www.energystar.gov/ia/partners/prod_development/revisions/downloads/computer/Version5.0_Computer_Spec.pdf

  Also to better help understand Energy Star. The Open Suse team actually 
heavily looked into this, and have a great presentation here:
  http://files.opensuse.org/opensuse/en/3/34/EnergyStar.pdf

  The reason you want to be Energy star compliant:

  - Many retailers will not sell machines that are not Energy Star compliant
  - Most Government agencies will not buy hardware solutions that are not 
Energy Star compliant
  - OEMs are now pushing heavily to have all hardware be Energy Star compliant
   - The OS software default settings are apart of the Energy Star 
compliance of machines

  There are only two default settings preventing Ubuntu from being energy star 
compliant:
  * Put display to Sleep within 15 minutes of user inactivity when on A/C
  - Currently this is set to 30 min. So setting it to 15 or below would 
fix this.
  * Activate computer's Sleep mode within 30 minutes of user inactivity when on 
A/C.
  - Currently this is set to never
  - It is also under stood that this could potentially have user 
experience impact

  If both settings cannot be done by deafult.  It has been requested to
  have an Energy Star button in Gnome Power Management interface that
  would set settings to be energy star compliant.

To manage notifications about this bug go to:
https://bugs.launchpad.net/chromium-browser/+bug/604635/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1771278] Re: search in gnome is not working

2018-05-16 Thread Matej 
Thank you Daniel.

You are right the vscode extension was the problem. After removing it
everything is back to normal.

I don't even remember installing it?!


Thank you for you fast response.

The problem is resolved.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-shell in Ubuntu.
https://bugs.launchpad.net/bugs/1771278

Title:
  search in gnome is not working

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  
  1)
  Description:  Ubuntu 18.04 LTS
  Release:  18.04

  2)
  gnome-shell:
Installed: 3.28.1-0ubuntu2
Candidate: 3.28.1-0ubuntu2
Version table:
   *** 3.28.1-0ubuntu2 500
  500 http://lu.archive.ubuntu.com/ubuntu bionic/main amd64 Packages
  100 /var/lib/dpkg/status


  3)
  When I press Super key and start typing to search, the results of the search 
should appear.

  4)
  Instead nothing happens.

  I see this errors in syslog.

  May 15 08:44:24 Acer18 gnome-shell[2385]: JS ERROR: TypeError:
  provider.display is
  
undefined#012_clearDisplay/<@resource:///org/gnome/shell/ui/search.js:605:13#012_clearDisplay@resource:///org/gnome/shell/ui/search.js:604:9#012wrapper@resource:///org/gnome/gjs/modules/_legacy.js:82:22#012_reset@resource:///org/gnome/shell/ui/search.js:495:9#012wrapper@resource:///org/gnome/gjs/modules/_legacy.js:82:22#012setTerms@resource:///org/gnome/shell/ui/search.js:555:13#012wrapper@resource:///org/gnome/gjs/modules/_legacy.js:82:22#012_onTextChanged@resource:///org/gnome/shell/ui/viewSelector.js:532:9#012wrapper@resource:///org/gnome/gjs/modules/_legacy.js:82:22#012reset@resource:///org/gnome/shell/ui/viewSelector.js:464:9#012wrapper@resource:///org/gnome/gjs/modules/_legacy.js:82:22#012show@resource:///org/gnome/shell/ui/viewSelector.js:284:9#012wrapper@resource:///org/gnome/gjs/modules/_legacy.js:82:22#012_animateVisible@resource:///org/gnome/shell/ui/overview.js:554:9#012wrapper@resource:///org/gnome/gjs/modules/_legacy.js:82:22#012show@resource:///org/gnome/shell/ui/overview.js:540:9#012wrapper@resource:///org/gnome/gjs/modules/_legacy.js:82:22#012toggle@resource:///org/gnome/shell/ui/overview.js:670:13#012wrapper@resource:///org/gnome/gjs/modules/_legacy.js:82:22#012_initializeUI/<@resource:///org/gnome/shell/ui/main.js:197:13

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-shell 3.28.1-0ubuntu2
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Uname: Linux 4.15.0-20-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Tue May 15 08:49:24 2018
  DisplayManager: gdm3
  GsettingsChanges:
   b'org.gnome.shell' b'enabled-extensions' 
b"['vscode-search-provi...@jomik.org']"
   b'org.gnome.shell' b'command-history' redacted by apport
   b'org.gnome.shell' b'app-picker-view' b'uint32 1'
   b'org.gnome.shell' b'favorite-apps' redacted by apport
   b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'"
  InstallationDate: Installed on 2018-05-02 (12 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

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

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1771278] [NEW] search in gnome is not working

2018-05-15 Thread Matej 
Public bug reported:


1)
Description:Ubuntu 18.04 LTS
Release:18.04

2)
gnome-shell:
  Installed: 3.28.1-0ubuntu2
  Candidate: 3.28.1-0ubuntu2
  Version table:
 *** 3.28.1-0ubuntu2 500
500 http://lu.archive.ubuntu.com/ubuntu bionic/main amd64 Packages
100 /var/lib/dpkg/status


3)
When I press Super key and start typing to search, the results of the search 
should appear.

4)
Instead nothing happens.

I see this errors in syslog.

May 15 08:44:24 Acer18 gnome-shell[2385]: JS ERROR: TypeError:
provider.display is
undefined#012_clearDisplay/<@resource:///org/gnome/shell/ui/search.js:605:13#012_clearDisplay@resource:///org/gnome/shell/ui/search.js:604:9#012wrapper@resource:///org/gnome/gjs/modules/_legacy.js:82:22#012_reset@resource:///org/gnome/shell/ui/search.js:495:9#012wrapper@resource:///org/gnome/gjs/modules/_legacy.js:82:22#012setTerms@resource:///org/gnome/shell/ui/search.js:555:13#012wrapper@resource:///org/gnome/gjs/modules/_legacy.js:82:22#012_onTextChanged@resource:///org/gnome/shell/ui/viewSelector.js:532:9#012wrapper@resource:///org/gnome/gjs/modules/_legacy.js:82:22#012reset@resource:///org/gnome/shell/ui/viewSelector.js:464:9#012wrapper@resource:///org/gnome/gjs/modules/_legacy.js:82:22#012show@resource:///org/gnome/shell/ui/viewSelector.js:284:9#012wrapper@resource:///org/gnome/gjs/modules/_legacy.js:82:22#012_animateVisible@resource:///org/gnome/shell/ui/overview.js:554:9#012wrapper@resource:///org/gnome/gjs/modules/_legacy.js:82:22#012show@resource:///org/gnome/shell/ui/overview.js:540:9#012wrapper@resource:///org/gnome/gjs/modules/_legacy.js:82:22#012toggle@resource:///org/gnome/shell/ui/overview.js:670:13#012wrapper@resource:///org/gnome/gjs/modules/_legacy.js:82:22#012_initializeUI/<@resource:///org/gnome/shell/ui/main.js:197:13

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: gnome-shell 3.28.1-0ubuntu2
ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
Uname: Linux 4.15.0-20-generic x86_64
ApportVersion: 2.20.9-0ubuntu7
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Tue May 15 08:49:24 2018
DisplayManager: gdm3
GsettingsChanges:
 b'org.gnome.shell' b'enabled-extensions' 
b"['vscode-search-provi...@jomik.org']"
 b'org.gnome.shell' b'command-history' redacted by apport
 b'org.gnome.shell' b'app-picker-view' b'uint32 1'
 b'org.gnome.shell' b'favorite-apps' redacted by apport
 b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'"
InstallationDate: Installed on 2018-05-02 (12 days ago)
InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
SourcePackage: gnome-shell
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug bionic

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-shell in Ubuntu.
https://bugs.launchpad.net/bugs/1771278

Title:
  search in gnome is not working

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  
  1)
  Description:  Ubuntu 18.04 LTS
  Release:  18.04

  2)
  gnome-shell:
Installed: 3.28.1-0ubuntu2
Candidate: 3.28.1-0ubuntu2
Version table:
   *** 3.28.1-0ubuntu2 500
  500 http://lu.archive.ubuntu.com/ubuntu bionic/main amd64 Packages
  100 /var/lib/dpkg/status


  3)
  When I press Super key and start typing to search, the results of the search 
should appear.

  4)
  Instead nothing happens.

  I see this errors in syslog.

  May 15 08:44:24 Acer18 gnome-shell[2385]: JS ERROR: TypeError:
  provider.display is
  
undefined#012_clearDisplay/<@resource:///org/gnome/shell/ui/search.js:605:13#012_clearDisplay@resource:///org/gnome/shell/ui/search.js:604:9#012wrapper@resource:///org/gnome/gjs/modules/_legacy.js:82:22#012_reset@resource:///org/gnome/shell/ui/search.js:495:9#012wrapper@resource:///org/gnome/gjs/modules/_legacy.js:82:22#012setTerms@resource:///org/gnome/shell/ui/search.js:555:13#012wrapper@resource:///org/gnome/gjs/modules/_legacy.js:82:22#012_onTextChanged@resource:///org/gnome/shell/ui/viewSelector.js:532:9#012wrapper@resource:///org/gnome/gjs/modules/_legacy.js:82:22#012reset@resource:///org/gnome/shell/ui/viewSelector.js:464:9#012wrapper@resource:///org/gnome/gjs/modules/_legacy.js:82:22#012show@resource:///org/gnome/shell/ui/viewSelector.js:284:9#012wrapper@resource:///org/gnome/gjs/modules/_legacy.js:82:22#012_animateVisible@resource:///org/gnome/shell/ui/overview.js:554:9#012wrapper@resource:///org/gnome/gjs/modules/_legacy.js:82:22#012show@resource:///org/gnome/shell/ui/overview.js:540:9#012wrapper@resource:///org/gnome/gjs/modules/_legacy.js:82:22#012toggle@resource:///org/gnome/shell/ui/overview.js:670:13#012wrapper@resource:///org/gnome/gjs/modules/_legacy.js:82:22#012_initializeUI/<@resource:///org/gnome/shell/ui/main.js:197:13

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-shell 3.28.1-0ubuntu2

[Desktop-packages] [Bug 1589215] Re: 'Unknown Application Name' menu item in Indicator Applet Appmenu when LibreOffice is running

2017-09-05 Thread Matej Kovacic 
I can confirm this issue. I have fresh install of 17.04, and it happens
when LO is started by clicking on an document. If LO is started from the
launcher or from the dash, this will not appear.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to libreoffice in Ubuntu.
https://bugs.launchpad.net/bugs/1589215

Title:
  'Unknown Application Name' menu item in Indicator Applet Appmenu when
  LibreOffice is running

Status in libreoffice package in Ubuntu:
  Confirmed

Bug description:
  Sometimes I get the issue of a menu having the name of a different
  application and being unusable, or being an application menu for the
  focused window but being titled 'Unknown Application Name', with
  LibreOffice. I also get this with GNOME apps but was told that this is
  a separate issue to the one I reported here:
  https://bugs.launchpad.net/ubuntu/+source/gnome-
  calculator/+bug/1584720 (see comment #5).

  The issue is with using Indicator Applet Appmenu in the panel on
  gnome-flashback installed on standard Ubuntu (which I call Ubuntu
  (GNOME) Flashback).

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: libreoffice-writer 1:5.1.3-0ubuntu4
  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
  CurrentDesktop: GNOME-Flashback:Unity
  Date: Sun Jun  5 10:32:35 2016
  InstallationDate: Installed on 2016-04-26 (39 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Alpha amd64 (20160426)
  SourcePackage: libreoffice
  UpgradeStatus: No upgrade log present (probably fresh install)

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

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 875676] Re: Backing up fails with 'IOError CRC check failed'.

2017-01-30 Thread Matej Kovacic 
No that it is not good. This is completely irresponsible and lame.

It is a shame, that so important software is a part of core Ubuntu
system. Canonical should reconsider using it. Because backup is critical
and if DejaDup is a part of a core system, people rely on it.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to deja-dup in Ubuntu.
https://bugs.launchpad.net/bugs/875676

Title:
  Backing up fails with 'IOError CRC check failed'.

Status in Déjà Dup:
  New
Status in Duplicity:
  New
Status in deja-dup package in Ubuntu:
  Confirmed

Bug description:
  For 4 days déjà dup hasn't been able to perform a backup. It fails
  with the error

  Failed to read /tmp/duplicity-lJcUDl-tempdir/mktemp-o4LYSJ-1: (, IOError('CRC check failed 0x8434f7d2L !=
  0x3d503338L',), )

  There is another similar bug #676767 where deleting ~/.cache/deja-dup
  helps. In this case it doesn't.

  I'm quite certain that my backup drive isn't corrupted. (It's a
  raid5.) I'd be happy to provide any additional information needed.

  --

  System information:
  Ubuntu 11.10
  deja-dup 20.0-0ubuntu3
  duplicity 0.6.15-0ubuntu2

  Logs:
  deja-dup.log: http://pastie.org/2705320
  deja-dup.gsettings: http://pastie.org/2705322

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

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 875676] Re: Backing up fails with 'IOError CRC check failed'.

2016-10-14 Thread Matej Kovacic 
I have the same error with DejaDup in Ubuntu 16.04.

I am trying to run a backup (not restore!), and got this error:

Ni mogoče brati /tmp/duplicity-gUZKem-tempdir/mktemp-jecFmU-5: (, IOError('CRC check failed 0x5528869f !=
0x2aeb4411L',), )

It is in slovenian, but it means:
Cannot read /tmp/duplicity-gUZKem-tempdir/mktemp-jecFmU-5: (, IOError('CRC check failed 0x5528869f != 0x2aeb4411L',), 
)

I tried to delete .cache/deja-dup, but the error is still there.

I am doing a backup to a remote server via ssh. I have reported this
under another bug, but it seems it belongs here.

Anyway, I deleted a file "duplicity-new-
signatures.20161011T065304Z.to.20161013T050922Z.sigtar.gz" on a backup
server, and now it is working (however, it started a new backup). But
this is really bad.

And just another question - would it be possible for me to restore
backup in that case?

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to deja-dup in Ubuntu.
https://bugs.launchpad.net/bugs/875676

Title:
  Backing up fails with 'IOError CRC check failed'.

Status in Déjà Dup:
  New
Status in Duplicity:
  New
Status in deja-dup package in Ubuntu:
  Confirmed

Bug description:
  For 4 days déjà dup hasn't been able to perform a backup. It fails
  with the error

  Failed to read /tmp/duplicity-lJcUDl-tempdir/mktemp-o4LYSJ-1: (, IOError('CRC check failed 0x8434f7d2L !=
  0x3d503338L',), )

  There is another similar bug #676767 where deleting ~/.cache/deja-dup
  helps. In this case it doesn't.

  I'm quite certain that my backup drive isn't corrupted. (It's a
  raid5.) I'd be happy to provide any additional information needed.

  --

  System information:
  Ubuntu 11.10
  deja-dup 20.0-0ubuntu3
  duplicity 0.6.15-0ubuntu2

  Logs:
  deja-dup.log: http://pastie.org/2705320
  deja-dup.gsettings: http://pastie.org/2705322

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

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 990584] Re: Caught an exception - System.MissingMethodException: Default constructor not found for type Mono.Upnp.Dcp.MediaServer1.ContentDirectory1.ClassReference. (in `mscorl

2014-02-23 Thread Matej Moško 
This is still an issue 2 years later. All media servers are greyed out
in UPNP section. Is there anything going to happen soon?

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to banshee in Ubuntu.
https://bugs.launchpad.net/bugs/990584

Title:
  Caught an exception - System.MissingMethodException: Default
  constructor not found for type
  Mono.Upnp.Dcp.MediaServer1.ContentDirectory1.ClassReference. (in
  `mscorlib')

Status in “banshee” package in Ubuntu:
  Fix Released
Status in “mono-upnp” package in Ubuntu:
  Fix Released
Status in “banshee” source package in Precise:
  In Progress
Status in “mono-upnp” source package in Precise:
  In Progress

Bug description:
  [24 Warn  17:38:41.927] Caught an exception - System.MissingMethodException: 
Default constructor not found for type 
Mono.Upnp.Dcp.MediaServer1.ContentDirectory1.ClassReference. (in `mscorlib')
at System.Activator.CreateInstance (System.Type type, Boolean nonPublic) 
[0x0] in filename unknown:0 
at 
Mono.Upnp.Xml.Compilation.DelegateDeserializationCompiler+CreateDeserializerc__AnonStoreyD.m__11
 (Mono.Upnp.Xml.XmlDeserializationContext context) [0x0] in filename 
unknown:0 
at 
Mono.Upnp.Xml.Compilation.DelegateDeserializationCompiler+CreateItemDeserializerc__AnonStorey1C.m__2F
 (System.Object obj, Mono.Upnp.Xml.XmlDeserializationContext context) [0x0] 
in filename unknown:0 
at 
Mono.Upnp.Xml.Compilation.DelegateDeserializationCompiler+CreateArrayItemElementDeserializerc__AnonStorey1E.m__31
 (System.Object obj, Mono.Upnp.Xml.XmlDeserializationContext context) [0x0] 
in filename unknown:0 
at 
Mono.Upnp.Xml.Compilation.DelegateDeserializationCompiler+CreateElementAutoDeserializerc__AnonStorey12.m__1A
 (System.Object obj, Mono.Upnp.Xml.XmlDeserializationContext context) [0x0] 
in filename unknown:0 
at Mono.Upnp.Xml.XmlDeserializer.AutoDeserializeElement[Container] 
(Mono.Upnp.Dcp.MediaServer1.ContentDirectory1.Container obj, 
Mono.Upnp.Xml.XmlDeserializationContext context) [0x0] in filename 
unknown:0 
at 
Mono.Upnp.Xml.XmlDeserializationContext.AutoDeserializeElement[Container] 
(Mono.Upnp.Dcp.MediaServer1.ContentDirectory1.Container obj) [0x0] in 
filename unknown:0 
at 
Mono.Upnp.Dcp.MediaServer1.ContentDirectory1.Container.DeserializeElement 
(Mono.Upnp.Xml.XmlDeserializationContext context) [0x0] in filename 
unknown:0 
at 
Mono.Upnp.Xml.XmlDeserializable.Mono.Upnp.Xml.IXmlDeserializable.DeserializeElement
 (Mono.Upnp.Xml.XmlDeserializationContext context) [0x0] in filename 
unknown:0 
at 
Mono.Upnp.Xml.Compilation.DelegateDeserializationCompiler.CreateSubElementDeserializerm__18
 (System.Object obj, Mono.Upnp.Xml.XmlDeserializationContext context) [0x0] 
in filename unknown:0 
at 
Mono.Upnp.Xml.Compilation.DelegateDeserializationCompiler+CreateElementDeserializerc__AnonStorey11.m__17
 (System.Object obj, Mono.Upnp.Xml.XmlDeserializationContext context, Int32 
depth) [0x0] in filename unknown:0 
  System.Reflection.TargetInvocationException: Exception has been thrown by the 
target of an invocation. (in `mscorlib')
at System.Reflection.MonoMethod.Invoke (System.Object obj, BindingFlags 
invokeAttr, System.Reflection.Binder binder, System.Object[] parameters, 
System.Globalization.CultureInfo culture) [0x0] in filename unknown:0 
at System.Reflection.MethodBase.Invoke (System.Object obj, System.Object[] 
parameters) [0x0] in filename unknown:0 
at 
Mono.Upnp.Dcp.MediaServer1.ContentDirectory1.RemoteContentDirectory+Deserializersc__Iterator5`1[Mono.Upnp.Dcp.MediaServer1.ContentDirectory1.Container].m__51
 (System.Xml.XmlReader reader) [0x0] in filename unknown:0 
at 
Mono.Upnp.Dcp.MediaServer1.ContentDirectory1.RemoteContentDirectory+Deserializec__Iterator6`1[Mono.Upnp.Dcp.MediaServer1.ContentDirectory1.Container].MoveNext
 () [0x0] in filename unknown:0 
at 
Mono.Upnp.Dcp.MediaServer1.ContentDirectory1.RemoteContentDirectory.GetObject[Container]
 (System.String id) [0x0] in filename unknown:0 
at 
Mono.Upnp.Dcp.MediaServer1.ContentDirectory1.RemoteContentDirectory.GetRootObject
 () [0x0] in filename unknown:0 
at Banshee.UPnPClient.UPnPServerSource.Parse (Mono.Upnp.Device device, 
Mono.Upnp.Dcp.MediaServer1.ContentDirectory1.ContentDirectoryController 
content_directory) [0x0] in filename unknown:0

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: banshee 2.4.0-2ubuntu1
  ProcVersionSignature: Ubuntu 3.2.0-24.37-generic 3.2.14
  Uname: Linux 3.2.0-24-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.0.1-0ubuntu7
  Architecture: amd64
  Date: Sat Apr 28 17:39:03 2012
  EcryptfsInUse: Yes
  InstallationMedia: Ubuntu 11.10 Oneiric Ocelot - Release amd64 (20111011)
  SourcePackage: banshee
  UpgradeStatus: Upgraded to precise on 2012-04-17 (10 days ago)

To manage notifications about this bug go to:

[Desktop-packages] [Bug 41179]

2013-01-16 Thread Matej 
(In reply to Murz from comment #63)
 So most of users stores Firefox passwords non-secured like as plain text,
 this is large security hole! 

No, it doesn't ... Firefox native password store is of course heavily
encrypted (although with only optional password, true).

Otherwise, +1 to comment 66 ... unless the solution works with Firefox
Sync (and thus with all those smartphones/tables) it couldn't be IMHO a
part of the native Firefox.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to firefox in Ubuntu.
https://bugs.launchpad.net/bugs/41179

Title:
  Integrate with Gnome Keyring

Status in The Mozilla Firefox Browser:
  Confirmed
Status in “firefox” package in Ubuntu:
  Won't Fix
Status in “xulrunner-1.9” package in Ubuntu:
  Won't Fix
Status in “xulrunner-1.9.1” package in Ubuntu:
  Triaged

Bug description:
  For a really good Gnome integration, it would be great to have the
  ability to save passwords in the Gnome keyring.

  A similar thing has been proposed for Epiphany: see
  https://launchpad.net/malone/bugs/3467.

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

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp