Dear Reporter,
Thank you for taking the time to report this bug and helping to make openSUSE
better.
We are sorry that we do not always have the capacity to look at all reported
bugs in a timely manner. There have been many changes in openSUSE since the
time you reported the bug and your pro
** Changed in: gnome-panel (openSUSE)
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-panel in Ubuntu.
https://bugs.launchpad.net/bugs/1006490
Title:
Gnome Classic 12.04 panel applet “F
This one seems to be solved in Wily.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to rhythmbox in Ubuntu.
https://bugs.launchpad.net/bugs/1479054
Title:
Shuffle and repeat buttons pressed state does not visually differ from
unpres
Created attachment 119174
Handle SEC_ERROR_UNTRUSTED_ISSUER
When verifying a PDF signed by a certificate issued by a CA not in the
trust store I would expect to get an error "Certificate isn't Trusted"
however currently the error message actually is the more generic
"Unknown issue with Certificate
I suggest we change the pdfsig "-c" switch to "-nocert". We can easily
add a single character option if we find it is needed. But we can't get
rid of it if we later regret it.
I'm still waiting for an answer to comment 79.
--
You received this bug notification because you are a member of Ubuntu
(In reply to Albert Astals Cid from comment #96)
> As said please let's not spend too much time on arguing over switch names,
> if you really really want -nocert, just push a patch to the
> signatureHandling branch that switches to it.
Done. I've also added a man page. If any further information t
(In reply to Adrian Johnson from comment #94)
> I suggest we change the pdfsig "-c" switch to "-nocert". We can easily add a
> single character option if we find it is needed. But we can't get rid of it
> if we later regret it.
>
> I'm still waiting for an answer to comment 79.
As said please let
I suggest we change the pdfsig "-c" switch to "-nocert". We can easily
add a single character option if we find it is needed. But we can't get
rid of it if we later regret it.
I'm still waiting for an answer to comment 79.
--
You received this bug notification because you are a member of Ubuntu
(In reply to Adrian Johnson from comment #79)
> + r_values[0] = r2.isInt64() ? r2.getInt64() : r2.getInt();
> + r_values[1] = r3.isInt64() ? r3.getInt64() : r3.getInt();
> + r_values[2] = r4.isInt64() ? r4.getInt64() : r4.getInt();
>
> According the PDF Reference, the ByteRange array contains
(In reply to Andre Guerreiro from comment #97)
> Quoting from ISO 32000-1 section 12.8.1:
> "This range should be the entire file, including the signature dictionary
> but excluding the signature value itself (the Contents entry). Other ranges
> may be used but since they do not check for all chan
(In reply to Adrian Johnson from comment #94)
> I suggest we change the pdfsig "-c" switch to "-nocert". We can easily add a
> single character option if we find it is needed. But we can't get rid of it
> if we later regret it.
>
> I'm still waiting for an answer to comment 79.
As said please let
(In reply to Adrian Johnson from comment #91)
> What is the output of "pkg-config --cflags nss"?
[user@dev-21 poppler]$ pkg-config --cflags nss
-I/usr/include/nss3 -I/usr/include/nspr4
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to e
(In reply to Markus Kilås from comment #93)
> Created attachment 119174 [details]
> Handle SEC_ERROR_UNTRUSTED_ISSUER
I pushed this and also some code to differentiate between an unknown and
an untrusted issuer (no idea what's the difference but if nss has this
difference i feel we also have to)
Created attachment 119283
Manpage improvement
Here's an improvement to the manpage.
Corrected a typo and added some missing context
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to evince in Ubuntu.
https://bugs.launchpad.net/bugs/108
(In reply to Adrian Johnson from comment #91)
> What is the output of "pkg-config --cflags nss"?
[user@dev-21 poppler]$ pkg-config --cflags nss
-I/usr/include/nss3 -I/usr/include/nspr4
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to p
(In reply to Andre Guerreiro from comment #100)
> Created attachment 119283 [details] [review]
> Manpage improvement
Pushed
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to evince in Ubuntu.
https://bugs.launchpad.net/bugs/1085526
Tit
Created attachment 119174
Handle SEC_ERROR_UNTRUSTED_ISSUER
When verifying a PDF signed by a certificate issued by a CA not in the
trust store I would expect to get an error "Certificate isn't Trusted"
however currently the error message actually is the more generic
"Unknown issue with Certificate
(In reply to Albert Astals Cid from comment #96)
> As said please let's not spend too much time on arguing over switch names,
> if you really really want -nocert, just push a patch to the
> signatureHandling branch that switches to it.
Done. I've also added a man page. If any further information t
(In reply to Markus Kilås from comment #93)
> Created attachment 119174 [details]
> Handle SEC_ERROR_UNTRUSTED_ISSUER
I pushed this and also some code to differentiate between an unknown and
an untrusted issuer (no idea what's the difference but if nss has this
difference i feel we also have to)
(In reply to Andre Guerreiro from comment #100)
> Created attachment 119283 [details] [review]
> Manpage improvement
Pushed
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to poppler in Ubuntu.
https://bugs.launchpad.net/bugs/740506
Tit
Created attachment 119283
Manpage improvement
Here's an improvement to the manpage.
Corrected a typo and added some missing context
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to poppler in Ubuntu.
https://bugs.launchpad.net/bugs/74
(In reply to Andre Guerreiro from comment #97)
> Quoting from ISO 32000-1 section 12.8.1:
> "This range should be the entire file, including the signature dictionary
> but excluding the signature value itself (the Contents entry). Other ranges
> may be used but since they do not check for all chan
(In reply to Adrian Johnson from comment #79)
> + r_values[0] = r2.isInt64() ? r2.getInt64() : r2.getInt();
> + r_values[1] = r3.isInt64() ? r3.getInt64() : r3.getInt();
> + r_values[2] = r4.isInt64() ? r4.getInt64() : r4.getInt();
>
> According the PDF Reference, the ByteRange array contains
Public bug reported:
Steps to reproduce:
1. open `nautilus` and create a new empty file `d` in your `$HOME` directory
with the `nautilus` context menu and move it to trash
2. right click on the trash icon in the `unity` launcher and click on `Empty
trash`
A new unnecessary `nautilus` windo
I've exactly the same bug in my Ubuntu 15.10. It seems related to
mount/umount commands, since mount mounts fstab entries marked as
"user", while umount cannot unmount the same entries.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to n
Sorry, I have to specify that I haven't non-western characters in my
fstav entries ...
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to nautilus in Ubuntu.
https://bugs.launchpad.net/bugs/1428417
Title:
Nautilus(and Nemo too) cannot
Public bug reported:
At the moment, the latest version of gnome-mahjongg [1] and shotwell [2]
fails to build from source on Xenial since one of the dependencies,
valac, is in Universe [3].
I don't know exactly how these decisions are made, but maybe vala needs
to be added to Main?
[1]
https://l
Installation of brasero-cdrkit does not resolve the problem in Ubuntu
Gnome 15.10.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to brasero in Ubuntu.
https://bugs.launchpad.net/bugs/783918
Title:
Brasero ejects CD before burning aud
Public bug reported:
The fcitx panel is wrong, it's using the charmap icon, instead a proper
monochrome one.
ProblemType: Bug
DistroRelease: Ubuntu 15.10
Package: fcitx 1:4.2.9-3
ProcVersionSignature: Ubuntu 4.2.0-14.16-generic 4.2.2
Uname: Linux 4.2.0-14-generic x86_64
ApportVersion: 2.19-0ubunt
** Package changed: fcitx (Ubuntu) => lubuntu-artwork (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to fcitx in Ubuntu.
https://bugs.launchpad.net/bugs/1511980
Title:
fcitx panel icon is wrong
To manage notifications about
According to this thread:
http://askubuntu.com/questions/459840/lock-screen-not-working-14-04
this problem is likely due to a bug in gnome-screensaver, in that the
14.04 package does not configure it to run at startup.
--
You received this bug notification because you are a member of Ubuntu
Des
Public bug reported:
The "Brightness & Lock" dialog reports that my screen should turn off
when inactive for 5 minutes, and it should require my password to
unlock, but this never happens. On a fresh install of 14.04, I've left
it idle for over an hour and the desktop remains visible and unlocked.
Public bug reported:
Required info:
1) Ubuntu 15.10
2) GNOME Terminal 3.16.2
3) Start instances of gnome-terminal with customized window title and icon
which are not grouped with default gnome-terminal instances
4) All instances gnome-terminal are grouped under the same icon, regardless of
what
Public bug reported:
I'm using Ubuntu 15.04.
apt-cache policy alacarte returns:
alacarte:
Installed: 3.11.91-2
Candidate: 3.11.91-2
Version table:
*** 3.11.91-2 0
500 http://us.archive.ubuntu.com/ubuntu/ vivid/universe amd64 Packages
100 /var/lib/dpkg/status
Last night I
** Description changed:
I'm using Ubuntu 15.04.
apt-cache policy alacarte returns:
alacarte:
- Installed: 3.11.91-2
- Candidate: 3.11.91-2
- Version table:
- *** 3.11.91-2 0
- 500 http://us.archive.ubuntu.com/ubuntu/ vivid/universe amd64 Packages
- 100 /var/lib/d
** Description changed:
I'm using Ubuntu 15.04.
apt-cache policy alacarte returns:
alacarte:
Installed: 3.11.91-2
Candidate: 3.11.91-2
Version table:
*** 3.11.91-2 0
500 http://us.archive.ubuntu.com/ubuntu/ vivid/universe amd64 Packages
100 /var/lib/d
Upstream Gnome bug:https://bugzilla.gnome.org/show_bug.cgi?id=749976
seems to refer to the same bug:
"When running in Unity, eog looks out of place due to the use of the
GtkHeaderBar. If we place the GtkHeaderBar where a traditional toolbar would be
and use the window manager decorations it
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: nautilus (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to nautilus in Ubuntu.
https://bugs.launchpad.net/bugs
broken on 15.04
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gstreamer0.10 in Ubuntu.
https://bugs.launchpad.net/bugs/1001738
Title:
Totem no longer play rtsp stream : black video-no sound
To manage notifications about this bug
[Expired for systemd (Ubuntu) because there has been no activity for 60
days.]
** Changed in: systemd (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to systemd in Ubuntu.
https://bugs.launch
40 matches
Mail list logo
