Hi guys!
I have filled a bug [1] with a strange problem after GNOME 3.22 update.
If I mount an USB stick that it is not in /etc/fstab, then I cannot
unmount it as a user using nautilus (or nemo). However, I saw one
person (zaitor) that is not having this problem. Hence, I am wondering
if anyone else can test this to see if it is a local problem.
Steps to reproduce
==================
1. Add an USB stick that is not listed in /etc/fstab
2. Try to unmount it using nautilus (Files).
3. Here, I see a message "Operation not permitted".
----------
[1] https://bugzilla.opensuse.org/show_bug.cgi?id=1001554
Best regards,
Ronan Arraes
--
To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org
Hello all
I installed Windows 10 on a friend's PC which has a 500 GB hard drive as well as a small SanDisk-SSD i100 24 GG flash drive. I pre formatted both drives NTFS before the install.
The fresh install of Win 10 ignored the existing SanDisk-SSD i100*. This seems like a bit of a waste. Yast2 reads the SanDisk-SSD i100 size as 22.37 Gio.
[*] Seen as /dev/sdb 22.37 Gio HPFS/NFDS NTFS under Yast2 on Leap42.2
I would like to install Leap42.2 on this machine using an EXT4 filesystem.
Note : I usually do something simple like this
Filesystem Size Used Avail Use% Mounted on
/dev/sda1 43G 27G 14G 67% /
Any advice in terms of the size to use to setup (via the Export mode using Yast2) the different (home, var partitions) filesystems (for a low maintenance setup) so that Leap42.2 can take advantage of the small and used SanDisk-SSD i100 24 GB flash drive would be greatly appreciated.
Many thanks in advance
Regards
James
--
To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org
I am curious if my /etc/os-release is odd:
# VERSION="20160913"
ID=opensuse
ID_LIKE="suse"
VERSION_ID="20160913"
PRETTY_NAME="openSUSE Tumbleweed"
ANSI_COLOR="0;32"
CPE_NAME="cpe:/o:opensuse:tumbleweed:20160913"
BUG_REPORT_URL="https://bugs.opensuse.org"
HOME_URL="https://www.opensuse.org/"
Should the VERSION line be commented as shown above? Or has something
odd happened to my file?
--
Roger Oberholtzer
--
To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org
Hi all,
I've been using the current build of freetype2 in
https://build.opensuse.org/package/show/M17N/freetype2, on Tumbleweed.
So far I've not had any issues using it, and the difference in quality
is remarkable depending on the screen used. On my laptop many slightly
blurry fonts are now razor sharp (medium hinting).
I tried to submit freetype2 to Leap 42.2 last week, but it was
declined due to some tests failing with libgd and python-pillow. As
I'm still somewhat new to the process, and even newer to the QA
testing used, I'm unsure of where to go from here. I've had a browse
through github and scanned the documentation I could find, but no
clear path sticks out to me, and I'm not seeing how those two packages
are failing the tests (I also can't find records of them in openQA).
Any guidance here would be much appreciated. I wish I could have done
this sooner, but I'm on a bit of a time constraint due to university
study.
Regards,
Luke.
--
To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org
Hi,
maybe it's just not obvious to me, but why would someone prefer virtualbox
over the native KVM virtualisation?
...ok, there is the option of using the same VM on linux, windows and Mac OS,
bus aside from that?
cheers
Mathias
--
gpg key fingerprint: 5F64 4C92 9B77 DE37 D184 C5F9 B013 44E7 27BD 763C
--
To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Hi all.
I download the 2nd Beta ISO, and tested in my laptop with Plasma Desktop
.
Looks great! But I have some minor issues in slideshow installation:
- - In many texts you can read "openSUSE Leap Leap 42.2". I left a
comment in weblate, but I don't know if someone read that comments :)
- - In the Developers and sysadmins slideshow, the image is a CD and a
musical note, maybe that's not the best image for that section.
- - After installation if you want to install something, you get an
error, because YaST can't get the installation media, so you have to
go to repo management and remove or disable. For newbies, maybe that
it's something annoying. It's not possible to remove or disable that
automatically?
I found some minor typos in spanish translation, that I have reviewed
via weblate.
've phun!
- --
GPG Key: 0xcc742e8dc9b7e22a
Aprende a proteger la privacidad de tu correo:
https://emailselfdefense.fsf.org/es/
Mi blog sobre openSUSE, GNU/Linux y software libre:
https://victorhckinthefreeworld.wordpress.com/
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2
iQIcBAEBAgAGBQJX6+UpAAoJEMx0Lo3Jt+IqCwcP/R4bkpcsMVfOOS1PuQ1ETP0f
4cubTgFfwcAf4w5Hv33fd4WexcNdDIZR6tPAwsejW9I+XCULcOO28UlPPA4U950K
d39m31a5eaIGEeYmWx0msi4n7n/se5miYO092aBAsf2WpoWYUE/aBN86+pV6oogB
Nhz0ZVN3BpZ0oHsUBNKiBICtecC7HvKwM6fy2t5/t3YBo5XD0ag+GYscrutsPE+g
Lb2jKyZVQYOI93uI3VcSNT0Cuh3i6yvzanVa+RtdhRz9+kDA8HbUhIzBa25lRLpA
5VJAT9/vLiXve4UAJznv3nAT7wKaqy2QFTS6cP4mRte/5oYBosRzC35GZ6OkZ/jg
tL5FCYTNiiIZNTc0bniXN2oL1NCKmbdMc29rNwISJp5KRETCXcs2Gb9nuC3WCSc6
uD77KFibORaDb3X7eYVWbHa6p5eZ7HTjZqdXopXXMRApvCJBPihRMcQy5QjyjKum
GO6agXzrN8Wz1ih/1aSbuO/t63D4Om0IwOX7AQ6dGEW20DG878Sn4hYu9Qjvh55l
PG0uqTgoYVEFRseGUJK3+uB5+oAticdl1W1kVu4OSX5MHircfsx/pRMhKf0tMgwy
w6t8PpwZbykcaUpyKgT5dmndju6rFuDaFNSjqu2BpeEWzpZYj8Lmh4PgQPuUyntK
5uo55h8W7JADUSh8uErK
=CF0d
-----END PGP SIGNATURE-----
--
To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org
Please note that this mail was generated by a script.
The described changes are computed based on the x86_64 DVD.
The full online repo contains too many changes to be listed here.
Please check the known defects of this snapshot before upgrading:
https://openqa.opensuse.org/tests/overview?distri=opensuse&groupid=1&versio…
When you reply to report some issues, make sure to change the subject.
It is not helpful to keep the release announcement subject in a thread
while discussing a specific problem.
Packages changed:
GraphicsMagick (1.3.24 -> 1.3.25)
acpica (20150717 -> 20160422)
libyui (3.2.6 -> 3.2.7)
mercurial (3.9 -> 3.9.1)
openssh
os-prober
vsftpd
xf86-input-keyboard
xf86-video-intel (2.99.917.674_g9154dff -> 2.99.917.703_b45dbdb)
yast2-core (3.1.23 -> 3.1.24)
yast2-ldap (3.1.13 -> 3.1.14)
yast2-mail (3.1.9 -> 3.1.10)
yast2-users (3.1.57 -> 3.1.60)
=== Details ===
==== GraphicsMagick ====
Version update (1.3.24 -> 1.3.25)
Subpackages: GraphicsMagick-devel libGraphicsMagick-Q16-3 libGraphicsMagick3-config libGraphicsMagickWand-Q16-2
- update to 1.3.25:
* EscapeParenthesis(): I was notified by Gustavo Grieco of a heap
overflow in EscapeParenthesis() used in the text annotation code.
While not being able to reproduce the issue, the implementation of
this function is completely redone.
* Utah RLE: Reject truncated/absurd files which caused huge memory
allocations and/or consumed huge CPU. Problem was reported by
Agostino Sarubbo based on testing with AFL.
* SVG/MVG: Fix another case of CVE-2016-2317 (heap buffer overflow) in
the MVG rendering code (also impacts SVG).
* TIFF: Fix heap buffer read overflow while copying sized TIFF
attributes. Problem was reported by Agostino Sarubbo based on
testing with AFL.
==== acpica ====
Version update (20150717 -> 20160422)
- enable build for ARM (needed for ovmf nowadays)
- Update to version 20160422
- Update to version 20151124
* Fixed a possible regression for a previous update to FADT handling. The
FADT no longer has a fixed table ID, causing some issues with code that
was hardwired to a specific ID. Lv Zheng.
* Fixed a problem where the method auto-serialization could interfere with
the current SyncLevel. This change makes the auto-serialization support
transparent to the SyncLevel support and management.
* Removed support for the _SUB predefined name in AcpiGetObjectInfo. This
interface is intended for early access to the namespace during the
initial namespace device discovery walk. The _SUB method has been seen to
access operation regions in some cases, causing errors because the
operation regions are not fully initialized.
* AML Debugger: Fixed some issues with the terminate/quit/exit commands
that can cause faults.
* AML Debugger: Add thread ID support so that single-step mode only applies
* to the AML Debugger thread. This prevents runtime errors within some
kernels.
* Eliminated extraneous warnings from AcpiGetSleepTypeData. Since the _Sx
methods that are invoked by this interface are optional, removed warnings
emitted for the case where one or more of these methods do not exist.
ACPICA BZ 1208.
* Made a major pass through the entire ACPICA source code base to
standardize formatting that has diverged a bit over time. There are no
functional changes, but this will of course cause quite a few code
differences from the previous ACPICA release.
* Example Code and Data Size: These are the sizes for the OS-independent
acpica.lib produced by the Microsoft Visual C++ 9.0 32-bit compiler. The
debug version of the code includes the debug output trace mechanism and
has a much larger code and data size.
* iASL/acpiexec/acpixtract/disassembler: Added support to allow multiple
definition blocks within a single ASL file and the resulting AML file.
Support for this type of file was also added to the various tools that
use binary AML files: acpiexec, acpixtract, and the AML disassembler. The
example code below shows two definition blocks within the same file:
DefinitionBlock ("dsdt.aml", "DSDT", 2, "Intel", "Template",
0x12345678)
{
}
DefinitionBlock ("", "SSDT", 2, "Intel", "Template", 0xABCDEF01)
{
}
* iASL: Enhanced typechecking for the Name() operator. All expressions for
the value of the named object must be reduced/folded to a single constant
at compile time, as per the ACPI specification (the AML definition of
Name()).
* iASL: Fixed some code indentation issues for the -ic and -ia options (C
and assembly headers). Now all emitted code correctly begins in column 1.
* iASL: Added an error message for an attempt to open a Scope() on an
object defined in an SSDT. The DSDT is always loaded into the namespace
first, so any attempt to open a Scope on an SSDT object will fail at
runtime.
- Remove acpica_remove_date_macro.patch; fixed on upstream release
==== libyui ====
Version update (3.2.6 -> 3.2.7)
- Added editing abilities to the spy dialog (Ctrl+Shift+Alt+Y
in the Qt UI) (bsc#998593)
- 3.2.7
==== mercurial ====
Version update (3.9 -> 3.9.1)
Subpackages: mercurial-lang
- Mercurial 3.9.1 (2016-9-1)
This is a regularly-scheduled bugfix release.
* bundle2: fail faster when interrupted
* bundle2: localize handleoutput remote prompts
* convert: move svn config initializer out of the module level
* debian: update source URL in copyright file
* exchange: correctly specify url to unbundle (issue5145)
* help: add example of '[templates]' usage
* help: update link to wiki/CommandServer
* osx: update bugzilla link in readme
* revset: fix keyword arguments to go through optimization process
* win32: update link to mailing list in readme
* win32: update wiki link in mercurial.ini
==== openssh ====
Subpackages: openssh-helpers
- FIPS compatibility (no selfchecks, only crypto restrictions)
[openssh-7.2p2-fips.patch]
- PRNG re-seeding
[openssh-7.2p2-seed-prng.patch]
- preliminary version of GSSAPI KEX
[openssh-7.2p2-gssapi_key_exchange.patch]
==== os-prober ====
- Parse /etc/os-release for openSUSE Tumbleweed (bsc#997465)
* os-prober-linux-distro-parse-os-release.patch
==== vsftpd ====
- Add vsftpd-3.0.2-fix-chown-uploads.patch to fix a bug in vsftpd
where files uploaded by an anonymous user could not be chown()ed
to the desired UID as specified in the daemon's configuration
file. [bnc#996370]
==== xf86-input-keyboard ====
- Add patch U_Use-xf86AddEnabledDevice-with-threaded-input.patch
This is in preparation for the upcoming XServer and its threaded input.
==== xf86-video-intel ====
Version update (2.99.917.674_g9154dff -> 2.99.917.703_b45dbdb)
- Fix the build against XServer 1.18.x or older
- Update to 2.99.917.703_b45dbdb:
Incremental update in preparation for XServer 1.19.
==== yast2-core ====
Version update (3.1.23 -> 3.1.24)
- disable doc generation (FATE#320356)
- remove unnecessary build dependency to speed up build
(bsc#999203)
- 3.1.24
==== yast2-ldap ====
Version update (3.1.13 -> 3.1.14)
- disable doc generation (FATE#320356)
- remove unnecessary build dependency to speed up build
(bsc#999203)
- 3.1.14
==== yast2-mail ====
Version update (3.1.9 -> 3.1.10)
- Reduce build dependencies to speed up build (bsc#999203)
- 3.1.10
==== yast2-users ====
Version update (3.1.57 -> 3.1.60)
- Do not require yast2-ldap for build time tests (bsc#999203).
- 3.1.60
- Prevent a potential security issue if the target authorized_keys
file is not a regular file (related to FATE#319471)
- Fix authorized_keys section of AutoYaST schema
- 3.1.59
- Add support to specify SSH authorized keys in the profile
(FATE#319471)
- 3.1.58
--
To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org
In celebration for our 25th Scrum sprint[1], we have published a new
sprint report. Enjoy it at
https://lizards.opensuse.org/?p=11983
Cheers.
[1] Yes, we publish one for every sprint. Still, it's always a
celebration ;)
--
Ancor González Sosa
YaST Team at SUSE Linux GmbH
--
To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org
On Wed, 2016-09-28 at 04:24 -0500, Jimmy Berry wrote:
> While we are on the subject note that the LSB release information
> does not seem to rebuild with the os-release information and is thus
> out of date.
That's pretty much by design - honestly, that info is utterly useless
to lsb-release and rebuilding this package daily really makes no sense
Cheers,
Dominique
I wish to test the smartcard support for pgp encryption in beta 2. (not Yubikey)
Before to get to a working result I had to follow these steps and I was done:
http://www.bress.net/blog/archives/203-How-to-use-a-cryptostick-with-Gnu-Pr…
Question:
a) is this still expected to require this user interaction to set up or should it work "out of the box".
b) is local(!) root login via such a token foreseen or has the feature not been implemented (using RSA signature for authentication).
c) is there any special function you would like me to try out for the sake of testing ( I will run signing, encrypting), i.e. I do not know if signing party is in the official repos and if it is expected to run. As it is a very widely used tool in signing parties, it would be good to know if it is functional. Does anybody know if this has been implemented (or is this packman and - in this case - does anybody know if packman will support beta2 with packages for testing?
d) does Kleopatra now handle crypto hardware or wasn't it still implemented?
The hardware is somewhat older but should be quite widely used especially in Germany and Northern Europe. A new version has been created by the producer https://blog.mozilla.org/security/files/2013/02/jpg-600x471..
Thank you.
---
Die Bundesliga hat begonnen! Alle Tore, alle Ergebnisse, alle News: Pocket Liga jetzt im https://app.adjust.com/dpynzd oder https://app.adjust.com/dpynzd herunterladen - kostenlos!
--
To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org