I'm not sure, if this is bug or feature... After few days, update applet (TW,
KDE) says there are 6843 new updates (TeX, R, ... ;-). When I click to
"Install updates" error "Too many packages to process (6843/5200)" appears.
Zypper handles it well. Is it worth of bug report? To b.o.o?
Yours,
V.
--
Vojtěch Zeisek
Komunita openSUSE GNU/Linuxu
Community of the openSUSE GNU/Linux
https://www.opensuse.org/https://trapa.cz/
Hi all,
After a TW update in the last few weeks, ssh with ssh-agent did
no longer work with my established setup. (I did not verify the
problem with a pristine user account, though).
I have set up my system (a loooong time ago... ;)) so that the
ssh key is stored somehow in gnome-keyring-daemon and gets unlocked
upon login.
The ssh-agent knows the key:
seife@strolchi:~> ssh-add -l
1024 SHA256:96ejSSf7kXLZRWhEE4oJUk20+RukUpSJOu4elrVABCU seife@strolchi (RSA)
...but it did not work:
seife@strolchi:~> ssh server
sign_and_send_pubkey: signing failed: agent refused operation
Password:
If I now refreshed the agent with "ssh-add", and entered my
passphrase, then ssh without password did work.
The journal showed the following:
Apr 08 18:28:41 strolchi gnome-keyring-daemon[1868]: the /usr/bin/ssh-add command failed: Child process exited with code 1
Apr 08 18:28:41 strolchi gnome-keyring-daemon[1868]: ssh_askpass: exec(/usr/lib/gcr-ssh-askpass): No such file or directory
So the solution was to install the gcr-ssh-askpass package (which
provides /usr/lib/gcr-ssh-askpass) and now everything is working
as before.
Hope this helps someone ;-)
--
Stefan Seyfried
"For a successful technology, reality must take precedence over
public relations, for nature cannot be fooled." -- Richard Feynman
--
To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org
Does anyone know if packager of OpenJDK is planning to also package
OpenJFX before JDK11 is released?
I write desktop Java applications using the JFX GUI toolkit in
addition to Swing. Having a reliable, continuously updated Java
environment on openSUSE products would be a great benefit for Java
developers.
I know nothing about building a distribution but if somebody wants to
hold my hand to explain how, I could throw some time at this project.
--
To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org
Hi, everyone!
My laptop is an Acer Aspire E15 with a built-in Bluetooth 4.0 adapter,
namely Qualcomm Atheros Bluetooth 4.0 (ID 04ca:3014).
I had to tweak Leap 42.3 for it work, here is a brief of what I did:
https://forums.opensuse.org/showthread.php/524410-Qualcomm-Atheros-Bluetoot…
Then I was using the kernel-default 4.13.6 and kernel-firmware from
the Kernel:stable OBS repo.
When I upgraded to Leap 15.0 Beta, I switched to the kernel-default
4.12.14 and kernel-firmware from the Leap 15.0 OSS repo.
Now, even though my Bluetooth adapter is working, I am not able to
pair with my headset (Philips SHB3060) using the A2DP profile.
I installed Blueman, which gives some more control and information
than GNOME's System Settings. Using Blueman, when I try to change my
headset to the A2DP profile I get this:
"Failed to change profile to a2dp_sink"
I tested downloading Leap 15.0 GNOME Live, flashing it into an USB
stick and booting from it. Bluetooth was not recognized at first, but
blacklisting the acer_wmi module (see my forum post for details) and
rebooting was enough. Then, Bluetooth worked normally (including
switching to the A2DP profile).
So, I believe it is a problem on my setup, not on Leap 15.0 itself,
i.e. a clean install would be half of the solution, the another half
blacklisting the acer_wmi module and rebooting.
Any ideas on what changed and how I can make the A2DP profile work again?
Thank you!
Antonio
The Linux Kamarada Project
http://kamarada.github.io/
--
To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org
Hi guys!
First of all, sorry if this is not the correct list to post something like this.
openSUSE has many mailing lists and some are very active. I, as a developer, must follow some to make sure I did not miss an important news. However, IMHO, mailing lists through e-mails are not that good anymore. It is very difficult to search for a message (if you did not archive everything, then you must rely on the on-line database), if you delete a message, reply to that thread is not very straightforward, etc.
I am wondering why do we not change to a more modern platform created with this kind of discussion in mind? In Julia project, they setup a discourse (http://discourse.julialang.org). It turn out that it is very good. In my opinion, much better than mailing lists using e-mails.
What do you think about this?
Cheers,
Ronan
Unfortunately I can't say when exactly this happened, but while I was
updating a Win7 laptop today I tried to log into it via krdc and that no
longer works. At first I thought it was related to the new firewalld,
but apparently there's some problem with Xcb?
Mar 14 19:48:40 Gertrud kwin_x11[2209]: QXcbConnection: XCB error: 3 (BadWindow), sequence: 50790, resource id: 56623169, major code: 19 (DeleteProperty), minor code: 0
Mar 14 19:48:40 Gertrud kwin_x11[2209]: QXcbConnection: XCB error: 3 (BadWindow), sequence: 50800, resource id: 56623169, major code: 19 (DeleteProperty), minor code: 0
Mar 14 19:48:40 Gertrud kwin_x11[2209]: QXcbConnection: XCB error: 3 (BadWindow), sequence: 50801, resource id: 56623169, major code: 18 (ChangeProperty), minor code: 0
Mar 14 19:48:40 Gertrud kwin_x11[2209]: QXcbConnection: XCB error: 3 (BadWindow), sequence: 50802, resource id: 56623169, major code: 19 (DeleteProperty), minor code: 0
Mar 14 19:48:40 Gertrud kwin_x11[2209]: QXcbConnection: XCB error: 3 (BadWindow), sequence: 50803, resource id: 56623169, major code: 19 (DeleteProperty), minor code: 0
Mar 14 19:48:40 Gertrud kwin_x11[2209]: QXcbConnection: XCB error: 3 (BadWindow), sequence: 50804, resource id: 56623169, major code: 19 (DeleteProperty), minor code: 0
Mar 14 19:48:40 Gertrud kwin_x11[2209]: QXcbConnection: XCB error: 3 (BadWindow), sequence: 50805, resource id: 56623169, major code: 7 (ReparentWindow), minor code: 0
Mar 14 19:48:40 Gertrud kwin_x11[2209]: QXcbConnection: XCB error: 3 (BadWindow), sequence: 50806, resource id: 56623169, major code: 6 (ChangeSaveSet), minor code: 0
Mar 14 19:48:40 Gertrud kwin_x11[2209]: QXcbConnection: XCB error: 3 (BadWindow), sequence: 50807, resource id: 56623169, major code: 2 (ChangeWindowAttributes), minor code: 0
Mar 14 19:48:40 Gertrud kwin_x11[2209]: QXcbConnection: XCB error: 3 (BadWindow), sequence: 50808, resource id: 56623169, major code: 10 (UnmapWindow), minor code: 0
Regards,
Achim.
--
+<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+
DIY Stuff:
http://Synth.Stromeko.net/DIY.html
--
To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org
Hello,
this looks like we have some haskell issue in Tumbleweed:
> Package 'xmonad' is not available in your repositories. Cannot
> reinstall, upgrade, or downgrade.
Is there some more information somewhere?
Thanks
Michal
--
To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org
Hello everyone,
Firstly I am cross posting this across a number of mailinglists because
this post affects several, but I would ask that you keep your replies /
feedback on the openSUSE project list as not to fragment discussion.
It has been raised with the board by several members of the community
that some of our mailinglists have not been working as effectively as we
would like. As such and as raised in our annual discussion with the
community during the conference, the board has decided to take a couple
of steps that we hope will resolve these issues or that will at least be
a starting point in resolving these issues.
Firstly we have created a new opensuse-support(a)o.o mailing list, we as
the board felt that in the transition from factory -> tumbleweed in
particular the change in role for opensuse(a)o.o did not work well and in
many cases there was an attitude that factory/tumbleweed issues should
still be posted on the factory mailing list. As such we have created the
support mailing list to help clarify these changes in policy that we
don't believe worked when we tried to change them last time. In short we
would like you to use opensuse-support(a)o.o whenever you require support
whether it is for Tumbleweed, Leap (regardless of whether you are using
a Leap beta or not) or any other project under the openSUSE umbrella.
This brings us to the next issue, posting bugs / bug reports on mailing
lists rather then bugzilla. This is a practice we would like to see
stopped and we will be gently reminding people if they continue posting
bugs on mailinglists, this especially includes if a package /
application breaks when updating tumbleweed / leap (including beta's).
We would ask that you search for your issue prior to reporting but in
case you accidentally report a duplicate bug its easy for us to mark it
as such, also if you report something that is intentional and not a bug
it doesn't take long to mark it as such, so if in doubt file a bug
rather then posting to a mailing list, there is useful information for
filing bugs at the following links [1][2]. But if you are really stuck
with trying to file your bug the friendly people at opensuse-support(a)o.o
can support you through the process.
The board hopes that with the changes outlined above the contents of the
opensuse-factory(a)o.o will go back to just being general distro
development discussion so if your post to openSUSE factory is something
other then that think twice about where the more appropriate place to
post is. The new tumbleweed snapshots will continue to be posted to
factory but we would ask you do not reply to them in order to report
issues / bugs. If a bug is reported that a package maintainer believes
will cause significant issues for most tumbleweed users ie not being
able to boot / login or severe data loss we still invite the maintainer
to post a warning to opensuse-factory but such issues happen very rarely
and as such we don't expect to see many such posts.
The board has decided that it would like to see how well these changes
work before deciding to add / remove / change openSUSE's mailing lists
further. Although we have discussed several other possibilities that we
could also try in the future.
1. https://en.opensuse.org/openSUSE:Bug_reporting_FAQ
2. https://en.opensuse.org/openSUSE:Submitting_bug_reports
--
Simon Lees (Simotek) http://simotek.net
Emergency Update Team keybase.io/simotek
SUSE Linux Adelaide Australia, UTC+10:30
GPG Fingerprint: 5B87 DB9D 88DC F606 E489 CEC5 0922 C246 02F0 014B
On 31/07/18 02:37 PM, Ronan Chagas wrote:
>>
>> That begs the question: why would it be easier if you DID archive everything?
>>
>
> My laptop has 256 GiB of SSD. It is impractical to clone my e-mails archive
> locally. So, in my laptop, if I want to search for a message and reply to it, I
> need to go to the online interface, search for the message, somehow send it to
> me, and then reply. Notice, I still have to access web to do this.
And therein lies the difference between Thee and Mee! (as the saying goes)
Using IMAP I download NOTING (except possibly, in passing, the headers for
threading). However I still have access to everything that is still 'current'
on the server.
What 'current' may mean depends on the ML's algorithm, but generally I see at
least a month on the openSUSE lists I subscribe to, and can scroll back that far.
Since the messages NEVER get downloaded from my server account @ my ISP until I
explicitly do so or explicitly 'archive' them to either the 'archive' folder'
there or to the 'archive' under Dovecot indexing on my home server, this is not
a problem.
As for your laptop, well 256G is marvellous coma[red to the 16G I have on my
tablet for reading email. So I NEVER EVER download onto the machine I use for
reading mail. EVER.
Of course you may have a cheapskate ISP that limits the number of messages you
can backlog, the time period or the amount of space. Like they say "YMMV"
Also like they say "Here's a nickel kid, get yourself a better computer", Or ISP.
http://dilbert.com/strip/1995-06-24
--
The universe we observe has precisely the properties we should expect if there
is, at bottom, no design, no purpose, no evil and no good, nothing but blind
pitiless indifference.
-- Richard Dawkins, River Out of Eden: A Darwinian View of Life (1995),
quoted from Victor J. Stenger, Has Science Found God? (2001)
--
To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org
Good evening,
quick question - once an update is accepted to Leap 15 Maintenance, when and
how is this pushed to openSUSE-Ports-Leap-15-Update Repo?
Thanks
Axel
--
To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org