[plasmashell] [Bug 485541] New: Plasma crash returning from blocked session

[Geraldo Simião]

https://bugs.kde.org/show_bug.cgi?id=485541

Bug ID: 485541
   Summary: Plasma crash returning from blocked session
Classification: Plasma
   Product: plasmashell
   Version: 6.0.3
  Platform: Fedora RPMs
OS: Linux
Status: REPORTED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: generic-crash
  Assignee: plasma-b...@kde.org
  Reporter: geraldo.simiao.k...@gmail.com
  Target Milestone: 1.0

Application: plasmashell (6.0.3)

Qt Version: 6.6.2
Frameworks Version: 6.0.0
Operating System: Linux 6.8.5-301.fc40.x86_64 x86_64
Windowing System: Wayland
Distribution: "Fedora Linux 40 (KDE Plasma)"
DrKonqi: 6.0.3 [CoredumpBackend]

-- Information about the crash:
Notebook was blocked all night, when I unblocked there was this crash warning.

The reporter is unsure if this crash is reproducible.

-- Backtrace:
Application: plasmashell (plasmashell), signal: Segmentation fault


This GDB supports auto-downloading debuginfo from the following URLs:
  
Enable debuginfod for this session? (y or [n]) [answered N; input not from
terminal]
Debuginfod has been disabled.
To make this setting permanent, add 'set debuginfod enabled off' to .gdbinit.
[New LWP 1794]
[New LWP 1817]
[New LWP 1826]
[New LWP 1825]
[New LWP 3033953]
[New LWP 19096]
[New LWP 1850]
[New LWP 2252]
[New LWP 1952]
[New LWP 1851]
[New LWP 5904]
[New LWP 2216]
[New LWP 2251]
[New LWP 5902]
[New LWP 1844]
[New LWP 2192]
[New LWP 3046]
[New LWP 3027]
[New LWP 2212]
[New LWP 3105]
[New LWP 2213]
[New LWP 3033954]
[New LWP 19095]
[New LWP 2253]
[New LWP 3028]
[New LWP 3104]
[New LWP 3106]
[New LWP 5903]
[New LWP 5905]
[New LWP 19097]
[New LWP 3033955]
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib64/libthread_db.so.1".
Core was generated by `/usr/bin/plasmashell --no-respawn'.
Program terminated with signal SIGSEGV, Segmentation fault.
#0  0x7f7ed94ab0f4 in __pthread_kill_implementation () from
/lib64/libc.so.6
[Current thread is 1 (Thread 0x7f7ed4b68b00 (LWP 1794))]
Cannot QML trace cores :(
[Current thread is 1 (Thread 0x7f7ed4b68b00 (LWP 1794))]

Thread 31 (Thread 0x7f7e48c006c0 (LWP 3033955)):
#0  0x7f7ed94a58c9 in __futex_abstimed_wait_common () at /lib64/libc.so.6
#1  0x7f7ed94a8299 in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libc.so.6
#2  0x7f7ebda9d71d in cnd_wait () at /usr/lib64/dri/crocus_dri.so
#3  0x7f7ebda7b31b in util_queue_thread_func () at
/usr/lib64/dri/crocus_dri.so
#4  0x7f7ebda9d64c in impl_thrd_routine () at /usr/lib64/dri/crocus_dri.so
#5  0x7f7ed94a9167 in start_thread () at /lib64/libc.so.6
#6  0x7f7ed952b2dc in clone3 () at /lib64/libc.so.6

Thread 30 (Thread 0x7f7e4b4006c0 (LWP 19097)):
#0  0x7f7ed94a58c9 in __futex_abstimed_wait_common () at /lib64/libc.so.6
#1  0x7f7ed94a8299 in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libc.so.6
#2  0x7f7ebda9d71d in cnd_wait () at /usr/lib64/dri/crocus_dri.so
#3  0x7f7ebda7b31b in util_queue_thread_func () at
/usr/lib64/dri/crocus_dri.so
#4  0x7f7ebda9d64c in impl_thrd_routine () at /usr/lib64/dri/crocus_dri.so
#5  0x7f7ed94a9167 in start_thread () at /lib64/libc.so.6
#6  0x7f7ed952b2dc in clone3 () at /lib64/libc.so.6

Thread 29 (Thread 0x7f7e860006c0 (LWP 5905)):
#0  0x7f7ed951d66d in poll () at /lib64/libc.so.6
#1  0x7f7ed8776724 in g_main_context_iterate_unlocked.isra () at
/lib64/libglib-2.0.so.0
#2  0x7f7ed871b647 in g_main_loop_run () at /lib64/libglib-2.0.so.0
#3  0x7f7ed5082e42 in gdbus_shared_thread_func.lto_priv () at
/lib64/libgio-2.0.so.0
#4  0x7f7ed87458a3 in g_thread_proxy () at /lib64/libglib-2.0.so.0
#5  0x7f7ed94a9167 in start_thread () at /lib64/libc.so.6
#6  0x7f7ed952b2dc in clone3 () at /lib64/libc.so.6

Thread 28 (Thread 0x7f7e99a006c0 (LWP 5903)):
#0  0x7f7ed951d66d in poll () at /lib64/libc.so.6
#1  0x7f7ed8776724 in g_main_context_iterate_unlocked.isra () at
/lib64/libglib-2.0.so.0
#2  0x7f7ed8716b03 in g_main_context_iteration () at
/lib64/libglib-2.0.so.0
#3  0x7f7ed8716b59 in glib_worker_main () at /lib64/libglib-2.0.so.0
#4  0x7f7ed87458a3 in g_thread_proxy () at /lib64/libglib-2.0.so.0
#5  0x7f7ed94a9167 in start_thread () at /lib64/libc.so.6
#6  0x7f7ed952b2dc in clone3 () at /lib64/libc.so.6

Thread 27 (Thread 0x7f7e6d0006c0 (LWP 3106)):
#0  0x7f7ed94a58c9 in __futex_abstimed_wait_common () at /lib64/libc.so.6
#1  0x7f7ed94a8299 in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libc.so.6
#2  0x7f7ebda9d71d in cnd_wait () at /usr/lib64/dri/crocus_dri.so
#3  0x7f7ebda7b31b in util_queue_thread_func () at
/usr/lib64/dri/crocus_dri.so
#4  0x7f7ebda9d64c in impl_thrd_routine () at /usr/lib64/dri/crocus_dri.so
#5  0x7f7ed94a9167 in start_thread () at /lib64/libc.so.6
#6  0x7f7ed952b2dc in clone3 () at 

[plasma-systemmonitor] [Bug 482169] System Monitor in Plasma 6 crashes on clicking "Show Details Sidebar"

[Geraldo Simião]

https://bugs.kde.org/show_bug.cgi?id=482169

Geraldo Simião  changed:

   What|Removed |Added

 CC||geraldo.simiao.kutz@gmail.c
   ||om

--- Comment #18 from Geraldo Simião  ---
Still happening on:
plasma-systemmonitor-6.0.3-1.fc40

Operating System: Fedora Linux 40
KDE Plasma Version: 6.0.3
KDE Frameworks Version: 6.0.0
Qt Version: 6.6.2

Kernel Version: 6.8.4-300.fc40.x86_64 (64-bit)

Graphics Platform: Wayland

Processors: 8 × Intel® Core™ i7-3632QM CPU @ 2.20GHz
Memory: 15.4 GiB of RAM
Graphics Processor: Mesa Intel® HD Graphics 4000
Manufacturer: Acer
Product Name: Aspire V3-571

Reproducible: Always

-- 
You are receiving this mail because:
You are watching all bug changes.

[plasma-systemmonitor] [Bug 484919] System Monitor crashes with segmentation fault

[Geraldo Simião]

https://bugs.kde.org/show_bug.cgi?id=484919

Geraldo Simião  changed:

   What|Removed |Added

 CC||geraldo.simiao.kutz@gmail.c
   ||om

--- Comment #2 from Geraldo Simião  ---
Can reproduce this on F40  KDE too.
plasma-systemmonitor-6.0.3-1.fc40

0::/user.slice/user-1000.slice/user@1000.service/app.slice/app-org.kde.plasma\x2dsystemmonitor-10da3a4ffad14ebeb24b62453b96eaba.scope

Operating System: Fedora Linux 40
KDE Plasma Version: 6.0.3
KDE Frameworks Version: 6.0.0
Qt Version: 6.6.2
Kernel Version: 6.8.4-300.fc40.x86_64 (64-bit)
Graphics Platform: Wayland
Processors: 8 × Intel® Core™ i7-3632QM CPU @ 2.20GHz
Memory: 15.4 GiB of RAM
Graphics Processor: Mesa Intel® HD Graphics 4000
Manufacturer: Acer
Product Name: Aspire V3-571

-- 
You are receiving this mail because:
You are watching all bug changes.

[khelpcenter] [Bug 484176] The KDE help center does not show the documentation for KDE applications.

[Geraldo Simião]

https://bugs.kde.org/show_bug.cgi?id=484176

--- Comment #6 from Geraldo Simião  ---
Created attachment 168018
  --> https://bugs.kde.org/attachment.cgi?id=168018=edit
Correct documentation page

-- 
You are receiving this mail because:
You are the assignee for the bug.

[khelpcenter] [Bug 484176] The KDE help center does not show the documentation for KDE applications.

[Geraldo Simião]

https://bugs.kde.org/show_bug.cgi?id=484176

--- Comment #6 from Geraldo Simião  ---
Created attachment 168018
  --> https://bugs.kde.org/attachment.cgi?id=168018=edit
Correct documentation page

-- 
You are receiving this mail because:
You are watching all bug changes.

[khelpcenter] [Bug 484176] The KDE help center does not show the documentation for KDE applications.

[Geraldo Simião]

https://bugs.kde.org/show_bug.cgi?id=484176

--- Comment #5 from Geraldo Simião  ---
Created attachment 168017
  --> https://bugs.kde.org/attachment.cgi?id=168017=edit
search results page

If I do a search on help center, for the same kcalc I found this results.
Clicking on the same chapter link it give me the correct doc.

-- 
You are receiving this mail because:
You are watching all bug changes.

[khelpcenter] [Bug 484176] The KDE help center does not show the documentation for KDE applications.

[Geraldo Simião]

https://bugs.kde.org/show_bug.cgi?id=484176

--- Comment #5 from Geraldo Simião  ---
Created attachment 168017
  --> https://bugs.kde.org/attachment.cgi?id=168017=edit
search results page

If I do a search on help center, for the same kcalc I found this results.
Clicking on the same chapter link it give me the correct doc.

-- 
You are receiving this mail because:
You are the assignee for the bug.

[khelpcenter] [Bug 484176] The KDE help center does not show the documentation for KDE applications.

[Geraldo Simião]

https://bugs.kde.org/show_bug.cgi?id=484176

--- Comment #4 from Geraldo Simião  ---
Created attachment 168016
  --> https://bugs.kde.org/attachment.cgi?id=168016=edit
Error documentation not found

-- 
You are receiving this mail because:
You are watching all bug changes.

[khelpcenter] [Bug 484176] The KDE help center does not show the documentation for KDE applications.

[Geraldo Simião]

https://bugs.kde.org/show_bug.cgi?id=484176

--- Comment #4 from Geraldo Simião  ---
Created attachment 168016
  --> https://bugs.kde.org/attachment.cgi?id=168016=edit
Error documentation not found

-- 
You are receiving this mail because:
You are the assignee for the bug.

[khelpcenter] [Bug 484176] The KDE help center does not show the documentation for KDE applications.

[Geraldo Simião]

https://bugs.kde.org/show_bug.cgi?id=484176

--- Comment #3 from Geraldo Simião  ---
Created attachment 168015
  --> https://bugs.kde.org/attachment.cgi?id=168015=edit
Screenshot using F1 and clicking on the title page

-- 
You are receiving this mail because:
You are the assignee for the bug.

[khelpcenter] [Bug 484176] The KDE help center does not show the documentation for KDE applications.

[Geraldo Simião]

https://bugs.kde.org/show_bug.cgi?id=484176

--- Comment #3 from Geraldo Simião  ---
Created attachment 168015
  --> https://bugs.kde.org/attachment.cgi?id=168015=edit
Screenshot using F1 and clicking on the title page

-- 
You are receiving this mail because:
You are watching all bug changes.

[khelpcenter] [Bug 484176] The KDE help center does not show the documentation for KDE applications.

[Geraldo Simião]

https://bugs.kde.org/show_bug.cgi?id=484176

Geraldo Simião  changed:

   What|Removed |Added

 CC||geraldo.simiao.kutz@gmail.c
   ||om

--- Comment #2 from Geraldo Simião  ---
Bug still present on khelpcenter-24.02.1-1.fc40.x86_64. If you just press F1
and then click on any chapter from the title page it shows the "documentation
not found" page. BUT, if you browse through the helpcenter (or use search) and
then arrive a the title page for kcalc (for example) THEN you can click on the
topic you want and open the right page.

-- 
You are receiving this mail because:
You are watching all bug changes.

[khelpcenter] [Bug 484176] The KDE help center does not show the documentation for KDE applications.

[Geraldo Simião]

https://bugs.kde.org/show_bug.cgi?id=484176

Geraldo Simião  changed:

   What|Removed |Added

 CC||geraldo.simiao.kutz@gmail.c
   ||om

--- Comment #2 from Geraldo Simião  ---
Bug still present on khelpcenter-24.02.1-1.fc40.x86_64. If you just press F1
and then click on any chapter from the title page it shows the "documentation
not found" page. BUT, if you browse through the helpcenter (or use search) and
then arrive a the title page for kcalc (for example) THEN you can click on the
topic you want and open the right page.

-- 
You are receiving this mail because:
You are the assignee for the bug.

Re: Donate 1 minute of your time to test upgrades from F39 to F40

[Geraldo Simião Kutz]

*This are the repos enabled here:*
id do repo  nome do repo
fedora  Fedora 39 - x86_64
fedora-cisco-openh264   Fedora 39 openh264 (From Cisco) - x86_64
google-chrome-beta  google-chrome-beta
rpmfusion-free  RPM Fusion for Fedora 39 - Free
rpmfusion-free-tainted  RPM Fusion for Fedora 39 - Free tainted
rpmfusion-free-updates  RPM Fusion for Fedora 39 - Free -
Updates
rpmfusion-free-updates-testing  RPM Fusion for Fedora 39 - Free - Test
Updates
rpmfusion-nonfree   RPM Fusion for Fedora 39 - Nonfree
rpmfusion-nonfree-updates   RPM Fusion for Fedora 39 - Nonfree -
Updates
rpmfusion-nonfree-updates-testing   RPM Fusion for Fedora 39 - Nonfree -
Test Updates
updates Fedora 39 - x86_64 - Updates
updates-testing Fedora 39 - x86_64 - Test Updates

*This was the command used:* *sudo dnf system-upgrade download
--releasever=40*

*This was the output:*
Erro:
 Problema: solicitações conflitantes
  - package libva-intel-media-driver-24.1.3-1.fc40.i686 from fedora
conflicts with intel-media-driver provided by
intel-media-driver-24.1.3-1.fc40.x86_64 from rpmfusion-nonfree
  - package libva-intel-media-driver-24.1.3-1.fc40.x86_64 from fedora
conflicts with intel-media-driver provided by
intel-media-driver-24.1.3-1.fc40.x86_64 from rpmfusion-nonfree
  - problema com o pacote instalado libva-2.20.0-2.fc39.x86_64
  - libva-2.20.0-2.fc39.x86_64 from @System  does not belong to a
distupgrade repository

*With this other command:* *sudo dnf system-upgrade download
--releasever=40 --allowerasing --best*

*I got this result:*
Erro:
 Problema: solicitações conflitantes
  - package gstreamer1-plugins-bad-free-1.22.9-3.fc40.x86_64 from fedora
requires libva.so.2()(64bit), but none of the providers can be installed
  - package libva-intel-media-driver-24.1.3-1.fc40.x86_64 from fedora
conflicts with intel-media-driver provided by
intel-media-driver-24.1.3-1.fc40.x86_64 from rpmfusion-nonfree
  - package vlc-plugin-gstreamer-1:3.0.20-12.fc40.x86_64 from fedora
requires gstreamer1-plugins-bad-free(x86-64), but none of the providers can
be installed
  - não é possível instalar o melhor candidato para a tarefa
  - libva-2.20.0-2.fc39.x86_64 from @System  does not belong to a
distupgrade repository
  - gstreamer1-plugins-bad-free-1.22.9-1.fc39.x86_64 from @System  does not
belong to a distupgrade repository

*But **then I removed gstreamer1-plugins-bad-free and run:*  *sudo dnf
system-upgrade download --releasever=40 --allowerasing --best
--exclude=libva-intel-media-driver,gstreamer1-plugins-bad-free,vlc-plugin-gstreamer,libva*

and the upgrade did proceed without errors.

Now I'm on F40 KDE and all is working fine (already upgraded libva and
reinstalled gstreamer1-plugins-bad-free)


Em qua., 21 de fev. de 2024 às 04:12, Miroslav Suchý 
escreveu:

> Do you want to make Fedora 40 better? Please spend 1 minute of your time
> and try to run:
>
> # Run this only if you use default Fedora modules
> # next time you run any DNF command default modules will be enabled again
> # This is last time we should do that :)
>
> sudo dnf module reset '*'
>
> dnf --releasever=40 --setopt=module_platform_id=platform:f40 \
> --enablerepo=updates-testing \
> $(rpm -q fedora-repos-modular >/dev/null && echo
> --enablerepo=updates-testing-modular) \
> --assumeno distro-sync
>
>
> This command does not replace `dnf system-upgrade`, but it will reveal
> potential problems.
>
> You may also run `dnf upgrade` before running this command.
>
> The `--assumeno` will just test the transaction, but does not make the
> actual upgrade.
>
>
> In case you hit dependency issues, please report it against the
> appropriate package.
>
> Or against fedora-obsolete-packages if that package should be removed in
> Fedora 40. Please check existing reports against fedora-obsolete-packages
> first:
>
> https://red.ht/2kuBDPu
>
> and also there is already bunch of "Fails to install" (F40FailsToInstall)
> reports:
>
>
> https://bugzilla.redhat.com/buglist.cgi?bug_id=2231790_id_type=anddependson=tvp_id=13416789
>
>
> Two notes:
>
> * you may want to run the same command with dnf5 to help test new dnf. Do
> not forget to add --best otherwise DNF5 hides all problems.
>
> * this command found several issues on my workstation. One was issue with
> teamd that you will likely hit too:
>
>   https://bugzilla.redhat.com/show_bug.cgi?id=2263334
>
> and there was few other with missing provides/obsoletes that I reported.
> For convenience here is the relevant part of Fedora Guidelines:
>
>
> https://docs.fedoraproject.org/en-US/packaging-guidelines/#renaming-or-replacing-existing-packages
>
>
> Thank you
> Miroslav
> --
> ___
> devel mailing list -- devel@lists.fedoraproject.org
> To unsubscribe send an email to devel-le...@lists.fedoraproject.org
> Fedora 

Re: Donate 1 minute of your time to test upgrades from F38 to F39

[Geraldo Simião Kutz]

Only this errors, none of them look like real problems:

Erro:
Problema 1: problema com o pacote instalado
telegram-desktop-4.8.4-3.fc38.x86_64
 - telegram-desktop-4.8.4-3.fc38.x86_64 from @System  does not belong to a
distupgrade repository
 - nothing provides qt6-qtbase(x86-64) = 6.5.1 needed by
telegram-desktop-4.8.4-2.fc39.x86_64 from rpmfusion-free
Problema 2: problema com o pacote instalado
igt-gpu-tools-1.26-3.20220508gitcffa5ff.fc38.x86_64
 - package igt-gpu-tools-1.26-3.20220508gitcffa5ff.fc38.x86_64 from @System
requires libprocps.so.8()(64bit), but none of the providers can be
installed
 - package igt-gpu-tools-1.26-3.20220508gitcffa5ff.fc38.x86_64 from @System
requires libprocps.so.8(LIBPROCPS_0)(64bit), but none of the providers can
be installed
 - package igt-gpu-tools-1.26-3.20220508gitcffa5ff.fc38.x86_64 from fedora
requires libprocps.so.8()(64bit), but none of the providers can be
installed
 - package igt-gpu-tools-1.26-3.20220508gitcffa5ff.fc38.x86_64 from fedora
requires libprocps.so.8(LIBPROCPS_0)(64bit), but none of the providers can
be installed
 - package igt-gpu-tools-1.26-3.20220508gitcffa5ff.fc38.x86_64 from
fedora-modular requires libprocps.so.8()(64bit), but none of the providers
can be installed
 - package igt-gpu-tools-1.26-3.20220508gitcffa5ff.fc38.x86_64 from
fedora-modular requires libprocps.so.8(LIBPROCPS_0)(64bit), but none of the
providers can be installed
 - package igt-gpu-tools-1.26-3.20220508gitcffa5ff.fc38.x86_64 from
updates-modular requires libprocps.so.8()(64bit), but none of the providers
can be installed
 - package igt-gpu-tools-1.26-3.20220508gitcffa5ff.fc38.x86_64 from
updates-modular requires libprocps.so.8(LIBPROCPS_0)(64bit), but none of
the providers can be installed
 - package igt-gpu-tools-1.26-3.20220508gitcffa5ff.fc38.x86_64 from
updates-testing-modular requires libprocps.so.8()(64bit), but none of the
providers can be installed
 - package igt-gpu-tools-1.26-3.20220508gitcffa5ff.fc38.x86_64 from
updates-testing-modular requires libprocps.so.8(LIBPROCPS_0)(64bit), but
none of the providers can be insta
lled
 - procps-ng-3.3.17-11.fc38.x86_64 from @System  does not belong to a
distupgrade repository
(tente adicionar '--skip-broken' para pular pacotes desinstaláveis)


Em qua., 23 de ago. de 2023 às 15:23, Miroslav Suchý 
escreveu:

> Do you want to make Fedora 39 better? Please spend 1 minute of your time
> and try to run:
>
> # Run this only if you use default Fedora modules
> # next time you run any DNF command default modules will be enabled again
> sudo dnf module reset '*'
>
> dnf --releasever=39 --setopt=module_platform_id=platform:f39 \
> --enablerepo=updates-testing \
> $(rpm -q fedora-repos-modular >/dev/null && echo
> --enablerepo=updates-testing-modular) \
> --assumeno distro-sync
>
>
> This command does not replace `dnf system-upgrade`, but it will reveal
> potential problems.
>
> You may also run `dnf upgrade` before running this command.
>
> The `--assumeno` will just test the transaction, but does not make the
> actual upgrade.
>
>
> In case you hit dependency issues, please report it against the
> appropriate package.
>
> Or against fedora-obsolete-packages if that package should be removed in
> Fedora 39. Please check existing reports against fedora-obsolete-packages
> first:
>
> https://red.ht/2kuBDPu
>
> and also there is already bunch of "Fails to install" (F39FailsToInstall)
> reports:
>
> https://bugzilla.redhat.com/buglist.cgi?bug_id=
> 2168845_id_type=anddependson=tvp_id=12486533
>
>
> Two notes:
>
> * you may want to run the same command with dnf5 to help test new dnf.
>
> * this command found zero issues on my personal system - great work all
> everybody!
>
>
> Thank you
> Miroslav
> ___
> devel mailing list -- devel@lists.fedoraproject.org
> To unsubscribe send an email to devel-le...@lists.fedoraproject.org
> Fedora Code of Conduct:
> https://docs.fedoraproject.org/en-US/project/code-of-conduct/
> List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
> List Archives:
> https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
> Do not reply to spam, report it:
> https://pagure.io/fedora-infrastructure/new_issue
>
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

[systemsettings] [Bug 467326] sddm-kcm should also synchronize CursorSize

[Geraldo Simião]

https://bugs.kde.org/show_bug.cgi?id=467326

--- Comment #9 from Geraldo Simião  ---
Created attachment 159268
  --> https://bugs.kde.org/attachment.cgi?id=159268=edit
apply plasma settings - apply

sddm.conf.d/kde_settings.conf after applying current settings (correct cursor
size was 24 on system settings)

-- 
You are receiving this mail because:
You are watching all bug changes.

[systemsettings] [Bug 467326] sddm-kcm should also synchronize CursorSize

[Geraldo Simião]

https://bugs.kde.org/show_bug.cgi?id=467326

--- Comment #8 from Geraldo Simião  ---
Created attachment 159267
  --> https://bugs.kde.org/attachment.cgi?id=159267=edit
apply plasma settings - reset to default

sddm.conf.d/kde_settings.conf after reset to default on system settings

-- 
You are receiving this mail because:
You are watching all bug changes.

[systemsettings] [Bug 467326] sddm-kcm should also synchronize CursorSize

[Geraldo Simião]

https://bugs.kde.org/show_bug.cgi?id=467326

--- Comment #7 from Geraldo Simião  ---
I tested on this setup and bug still present:

Operating System: Fedora Linux 38
KDE Plasma Version: 5.27.5
KDE Frameworks Version: 5.106.0
Qt Version: 5.15.9
Kernel Version: 6.3.3-200.fc38.x86_64 (64-bit)
Graphics Platform: Wayland

sddm-0.19.0^git20230404.e652433-1.fc38.x86_64
kde-settings-sddm-38.2-2.fc38.noarch
sddm-wayland-plasma-5.27.5-1.fc38.noarch
sddm-breeze-5.27.5-1.fc38.noarch
sddm-kcm-5.27.5-1.fc38.x86_64

plasma-systemsettings-5.27.5-1.fc38.x86_64

-- 
You are receiving this mail because:
You are watching all bug changes.

[systemsettings] [Bug 470024] New: kcm-sddm don't sync mouse cursor size to SDDM-wayland

[Geraldo Simião]

https://bugs.kde.org/show_bug.cgi?id=470024

Bug ID: 470024
   Summary: kcm-sddm don't sync mouse cursor size to SDDM-wayland
Classification: Applications
   Product: systemsettings
   Version: 5.27.5
  Platform: Fedora RPMs
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: kcm_sddm
  Assignee: k...@davidedmundson.co.uk
  Reporter: geraldo.simiao.k...@gmail.com
CC: k...@david-redondo.de, plasma-b...@kde.org
  Target Milestone: ---

SUMMARY
Using SDDM-wayland at F38 (and F37 too), when trying to export plasma
configurations to SDDM (theme, colors, etc) it doesn't export mouse cursor
size, and apparently when no cursor size is specified SDDM-wayland is
defaulting to size 36 which can look a bit odd (big) on some monitors.
When we open and manualy edit the file in /etc/sddm.conf.d/kde_settings.conf,
adding the line CursorSize=24 (or whatever you wanna use), then it works fine
(its a workaround, I know).

Reproducible: Always

Steps to Reproduce:
1.open plasma-systemsettings and set a specific cursor size (lets say 24)
2.go to login screen (SDDM) at system settings and apply plasma configurations
3.log out to check if cursor size is smaller than 36
Actual Results:  
The cursor size is always 36 no matter what you set and export at system
settings

Expected Results:  
The cursor size at SDDM follows what is set at cursor settings

Tested on F38 and F37 with this package versions:

Operating System: Fedora Linux 38
KDE Plasma Version: 5.27.5
KDE Frameworks Version: 5.106.0
Qt Version: 5.15.9
Kernel Version: 6.3.3-200.fc38.x86_64 (64-bit)
Graphics Platform: Wayland

sddm-0.19.0^git20230404.e652433-1.fc38.x86_64
kde-settings-sddm-38.2-2.fc38.noarch
sddm-wayland-plasma-5.27.5-1.fc38.noarch
sddm-breeze-5.27.5-1.fc38.noarch
sddm-kcm-5.27.5-1.fc38.x86_64

plasma-systemsettings-5.27.5-1.fc38.x86_64


ADDITIONAL INFORMATION

If CursorSize=24 exists on the themes group at kde_settings.conf, and I change
at system settings the cursor to a biger size (like 36 or 48) and then hit the
"Apply Plasma Settings" button, the cursor size change acordingly. But if we
wanna change the size for something smaller than 36, then it don't apply the
change.

Patch idea:
Maybe if we add something like this to this file at the "Theme" group, it will
create the right setting =>
https://invent.kde.org/plasma/sddm-kcm/-/blob/master/src/sddmsettings.kcfg
   
  defaultCursorSize()
  

-- 
You are receiving this mail because:
You are watching all bug changes.

[lokalize] [Bug 424024] Main window doesn't repaint correctly on Wayland

[Geraldo Simião]

https://bugs.kde.org/show_bug.cgi?id=424024

--- Comment #34 from Geraldo Simião  ---
Created attachment 158875
  --> https://bugs.kde.org/attachment.cgi?id=158875=edit
workaround is fine for now

Added ´´-platform xcb´´ to the launcher at menu edit and its correctly using
xwayland without problems on fedora 37 KDE spin.
Its a workaround indeed.

-- 
You are receiving this mail because:
You are watching all bug changes.

[lokalize] [Bug 424024] Main window doesn't repaint correctly on Wayland

[Geraldo Simião]

https://bugs.kde.org/show_bug.cgi?id=424024

Geraldo Simião  changed:

   What|Removed |Added

 CC||geraldo.simiao.kutz@gmail.c
   ||om

--- Comment #33 from Geraldo Simião  ---
Bug still present at my setup:

lokalize-23.04.0-1.fc37.x86_64

Operating System: Fedora Linux 37
KDE Plasma Version: 5.27.5
KDE Frameworks Version: 5.105.0
Qt Version: 5.15.9
Kernel Version: 6.2.15-200.fc37.x86_64 (64-bit)
Graphics Platform: Wayland
Processors: 8 × Intel® Core™ i7-3632QM CPU @ 2.20GHz
Memory: 15.4 GiB of RAM
Graphics Processor: Mesa Intel® HD Graphics 4000

kf5-kwindowsystem-5.105.0-1.fc37.x86_64
kf5-kxmlgui-5.105.0-1.fc37.x86_64
kwin-libs-5.27.5-1.fc37.x86_64
kwin-common-5.27.5-1.fc37.x86_64
kwin-x11-5.27.5-1.fc37.x86_64
kwin-wayland-5.27.5-1.fc37.x86_64
kwin-5.27.5-1.fc37.x86_64

-- 
You are receiving this mail because:
You are watching all bug changes.

[Linux-traipu] [Bug 2012150] Re: Can't edit title - inkscape won't open in Ubuntu/Linux

[Geraldo Fonseca]

RESOLVED
Sorted out

1- I completely deleted Openshot and Inkscape programs.
2- I reinstalled the programs in the following order:
a) first Openshot by Ubuntu -Deb mode (Program installer) 
b) and then I installed Inkscape the same way and also downloaded Appimagem 
(from Inkscape) .
3- I set the permissions through the terminal: chmod +x openshot.appimage
4- I pointed the Advanced Title Editor path to: /home/
"my step folder"/Downloads/Inkscape-b0a8486-x86_64.AppImage
And. voilá.. Success!

-- 
You received this bug notification because you are a member of UBUNTU -
AL - BR, which is subscribed to OpenShot Video Editor.
https://bugs.launchpad.net/bugs/2012150

Title:
  Can't edit title - inkscape won't open in Ubuntu/Linux

Status in OpenShot Video Editor:
  New

Bug description:
  Hey guys

  I cannot edit TITLE using the "Use Advanced Editor" option.
  I pointed the path to the Inkscape "executable" inside the corresponding 
folders/directories in Ubuntu, but Inkscape just won't open. And it doesn't 
show any error message. I'm still researching, but it's hard to find a 
solution. Could it be an Openshot bug?

  
  Architecture: 64 bits
  Operating System & version: Ubuntu 22.04.2 LTS
  Installation Method Ubuntu: i do not know
  Installation Method Openshot: Ubuntu Deb
  Installation Method Inkscape: Ubuntu Deb
  Version of Openshot installed: 3.0.0
  BZR Revision used (if any) :
  MLT/melt version:
  FFmpeg (i.e.libavcodec) version : n4.4.3-3
  FFmpeg installation : Snpap

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


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

[Openshot.bugs] [Bug 2012150] Re: Can't edit title - inkscape won't open in Ubuntu/Linux

[Geraldo Fonseca]

RESOLVED
Sorted out

1- I completely deleted Openshot and Inkscape programs.
2- I reinstalled the programs in the following order:
a) first Openshot by Ubuntu -Deb mode (Program installer) 
b) and then I installed Inkscape the same way and also downloaded Appimagem 
(from Inkscape) .
3- I set the permissions through the terminal: chmod +x openshot.appimage
4- I pointed the Advanced Title Editor path to: /home/
"my step folder"/Downloads/Inkscape-b0a8486-x86_64.AppImage
And. voilá.. Success!

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

Title:
  Can't edit title - inkscape won't open in Ubuntu/Linux

Status in OpenShot Video Editor:
  New

Bug description:
  Hey guys

  I cannot edit TITLE using the "Use Advanced Editor" option.
  I pointed the path to the Inkscape "executable" inside the corresponding 
folders/directories in Ubuntu, but Inkscape just won't open. And it doesn't 
show any error message. I'm still researching, but it's hard to find a 
solution. Could it be an Openshot bug?

  
  Architecture: 64 bits
  Operating System & version: Ubuntu 22.04.2 LTS
  Installation Method Ubuntu: i do not know
  Installation Method Openshot: Ubuntu Deb
  Installation Method Inkscape: Ubuntu Deb
  Version of Openshot installed: 3.0.0
  BZR Revision used (if any) :
  MLT/melt version:
  FFmpeg (i.e.libavcodec) version : n4.4.3-3
  FFmpeg installation : Snpap

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


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

[Openshot.bugs] [Bug 2012150] [NEW] Can't edit title - inkscape won't open in Ubuntu/Linux

[Geraldo Fonseca]

Public bug reported:

Hey guys

I cannot edit TITLE using the "Use Advanced Editor" option.
I pointed the path to the Inkscape "executable" inside the corresponding 
folders/directories in Ubuntu, but Inkscape just won't open. And it doesn't 
show any error message. I'm still researching, but it's hard to find a 
solution. Could it be an Openshot bug?


Architecture: 64 bits
Operating System & version: Ubuntu 22.04.2 LTS
Installation Method Ubuntu: i do not know
Installation Method Openshot: Ubuntu Deb
Installation Method Inkscape: Ubuntu Deb
Version of Openshot installed: 3.0.0
BZR Revision used (if any) :
MLT/melt version:
FFmpeg (i.e.libavcodec) version : n4.4.3-3
FFmpeg installation : Snpap

** Affects: openshot
 Importance: Undecided
 Status: New

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

Title:
  Can't edit title - inkscape won't open in Ubuntu/Linux

Status in OpenShot Video Editor:
  New

Bug description:
  Hey guys

  I cannot edit TITLE using the "Use Advanced Editor" option.
  I pointed the path to the Inkscape "executable" inside the corresponding 
folders/directories in Ubuntu, but Inkscape just won't open. And it doesn't 
show any error message. I'm still researching, but it's hard to find a 
solution. Could it be an Openshot bug?

  
  Architecture: 64 bits
  Operating System & version: Ubuntu 22.04.2 LTS
  Installation Method Ubuntu: i do not know
  Installation Method Openshot: Ubuntu Deb
  Installation Method Inkscape: Ubuntu Deb
  Version of Openshot installed: 3.0.0
  BZR Revision used (if any) :
  MLT/melt version:
  FFmpeg (i.e.libavcodec) version : n4.4.3-3
  FFmpeg installation : Snpap

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


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

[Linux-traipu] [Bug 2012150] [NEW] Can't edit title - inkscape won't open in Ubuntu/Linux

[Geraldo Fonseca]

Public bug reported:

Hey guys

I cannot edit TITLE using the "Use Advanced Editor" option.
I pointed the path to the Inkscape "executable" inside the corresponding 
folders/directories in Ubuntu, but Inkscape just won't open. And it doesn't 
show any error message. I'm still researching, but it's hard to find a 
solution. Could it be an Openshot bug?


Architecture: 64 bits
Operating System & version: Ubuntu 22.04.2 LTS
Installation Method Ubuntu: i do not know
Installation Method Openshot: Ubuntu Deb
Installation Method Inkscape: Ubuntu Deb
Version of Openshot installed: 3.0.0
BZR Revision used (if any) :
MLT/melt version:
FFmpeg (i.e.libavcodec) version : n4.4.3-3
FFmpeg installation : Snpap

** Affects: openshot
 Importance: Undecided
 Status: New

-- 
You received this bug notification because you are a member of UBUNTU -
AL - BR, which is subscribed to OpenShot Video Editor.
https://bugs.launchpad.net/bugs/2012150

Title:
  Can't edit title - inkscape won't open in Ubuntu/Linux

Status in OpenShot Video Editor:
  New

Bug description:
  Hey guys

  I cannot edit TITLE using the "Use Advanced Editor" option.
  I pointed the path to the Inkscape "executable" inside the corresponding 
folders/directories in Ubuntu, but Inkscape just won't open. And it doesn't 
show any error message. I'm still researching, but it's hard to find a 
solution. Could it be an Openshot bug?

  
  Architecture: 64 bits
  Operating System & version: Ubuntu 22.04.2 LTS
  Installation Method Ubuntu: i do not know
  Installation Method Openshot: Ubuntu Deb
  Installation Method Inkscape: Ubuntu Deb
  Version of Openshot installed: 3.0.0
  BZR Revision used (if any) :
  MLT/melt version:
  FFmpeg (i.e.libavcodec) version : n4.4.3-3
  FFmpeg installation : Snpap

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


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

Re: F38 dnf modules isn't going to be functional

[Geraldo Simião Kutz]

Dnf5 as default is a f39 proposal

https://fedoraproject.org/wiki/Releases/39/ChangeSet


https://fedoraproject.org/wiki/Changes/ReplaceDnfWithDnf5

Em qua, 15 de mar de 2023 04:32, Sumantro Mukherjee 
escreveu:

> DNF5 test day is running and we have figured that dnf modules command
> is being worked on.
> The functionality can be tracked [0] and this is targeted to be complete
> in F39.
> If users, have modules enabled in F37 and upgrade to F38, things will be
> fine.
> However, fresh installs or installations which wanna play with modules
> in F38 won't be
> able to do that.
>
> DNF team suggests a workaround how to modify modules without using any
> tool - modify files in /etc/dnf/modules.d. if you want to reset nodejs
> module you can use rm /etc/dnf/modules.d/nodejs
>
> If this is a problematic thing, we should communicate this to the users.
>
> [0] https://github.com/rpm-software-management/dnf5/issues/146
>
> --
> //sumantro
> Fedora QE
> TRIED AND PERSONALLY TESTED, ERGO TRUSTED
> ___
> test mailing list -- test@lists.fedoraproject.org
> To unsubscribe send an email to test-le...@lists.fedoraproject.org
> Fedora Code of Conduct:
> https://docs.fedoraproject.org/en-US/project/code-of-conduct/
> List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
> List Archives:
> https://lists.fedoraproject.org/archives/list/test@lists.fedoraproject.org
> Do not reply to spam, report it:
> https://pagure.io/fedora-infrastructure/new_issue
>
___
test mailing list -- test@lists.fedoraproject.org
To unsubscribe send an email to test-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/test@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

Re: Kernel 6.2 Test Week Invitation

[Geraldo Simião Kutz]

This is because the script testing the kernel failed to authenticate the
login to send the results to the Fedora infrastructure.
Its not a problem on the kernel, just some login information not configured
correctly.

Em dom, 5 de mar de 2023 11:39, Riya Bisht 
escreveu:

>  I tested Fedora 6.2.2-300.fc37.x86_64 and it passed both tests but it is
> showing me this error. Any idea about it?
>
> Traceback (most recent call last):
>   File "/home/liveuser/kernel-tests/./fedora_submit.py", line 43, in
> 
> submitclient.login(
>   File
> "/usr/lib/python3.11/site-packages/fedora/client/openidbaseclient.py", line
> 303, in login
> response = openid_login(
>^
>   File
> "/usr/lib/python3.11/site-packages/fedora/client/openidproxyclient.py",
> line 138, in openid_login
> raise AuthError(output['message'])
> fedora.client.AuthError: Authentication failed
> The following information is not submitted with your log;
> it is for informational purposes only.
> Checking for kernel signature:
> The signer's common name is Fedora Secure Boot Signer
> The signer's common name is kernel-signer
>
> On Fri, 3 Mar 2023 at 22:06, Sumantro Mukherjee 
> wrote:
>
>> Hey All,
>>
>> I would like to invite all of you to participate in the Kernel 6.2
>> Test week is happening from 2023-03-05 to 2023-03-12. It's
>> fairly simple, head over to the wiki [0] and read in detail about the
>> test week and simply run the test case mentioned in[1] and enter your
>> results.
>>
>> As usual, the Fedora QA team will hangout at #fedora-test-...@libera.chat
>> for question and discussion.
>>
>> [0]
>> http://fedoraproject.org/wiki/Test_Day:2023-03-05_Kernel_6.2_Test_Week
>> [1] https://testdays.fedoraproject.org/events/148
>>
>> --
>> //sumantro
>> Fedora QE
>> TRIED AND PERSONALLY TESTED, ERGO TRUSTED
>> ___
>> test mailing list -- test@lists.fedoraproject.org
>> To unsubscribe send an email to test-le...@lists.fedoraproject.org
>> Fedora Code of Conduct:
>> https://docs.fedoraproject.org/en-US/project/code-of-conduct/
>> List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
>> List Archives:
>> https://lists.fedoraproject.org/archives/list/test@lists.fedoraproject.org
>> Do not reply to spam, report it:
>> https://pagure.io/fedora-infrastructure/new_issue
>>
> ___
> test mailing list -- test@lists.fedoraproject.org
> To unsubscribe send an email to test-le...@lists.fedoraproject.org
> Fedora Code of Conduct:
> https://docs.fedoraproject.org/en-US/project/code-of-conduct/
> List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
> List Archives:
> https://lists.fedoraproject.org/archives/list/test@lists.fedoraproject.org
> Do not reply to spam, report it:
> https://pagure.io/fedora-infrastructure/new_issue
>
___
test mailing list -- test@lists.fedoraproject.org
To unsubscribe send an email to test-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/test@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

Re: Proposal: drop delta rpms (for real this time)

[Geraldo Simião Kutz]

Testing F38 KDE spin today, I see this:
Delta RPMs reduced 235.2 MB to 23.8 MB (89.9%)

So, it seems we do still have some cornercases when deltaRPM shows its
value.

But, ok, In agree that in most cases it's irrelevant this days.
+1 for dropping deltarpm

geraldosimiao



Em ter., 21 de fev. de 2023 às 17:48, Matthew Miller <
mat...@fedoraproject.org> escreveu:

> I was asked to weigh in on https://pagure.io/releng/issue/7215 as a
> priority. Last time we talked about this we didn't really get anywhere...
>
>
> https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org/thread/JYKVELSBJQMEK6KEFXG354ZDZDDX4C5G/#RLEUYSWOUVUS53YAP7WQQNN7HNEBIC4E
>
> ... and that ticket hasn't moved, because fixing it isn't trivial.
>
>
> What we're doing now — as has been the case for several years, already
> noted
> in the previous discussion — has very little end-user value. Also as noted
> in that thread (as in the ticket)... that's unfortunate, because it did
> bring some real benefits (and could possibly do even more.)
>
> But, I think it's time to move on. We have ostree and various
> container-delta approaches. We should focus on those — and give DeltaRPMs a
> sad, fond farewell.
>
> --
> Matthew Miller
> 
> Fedora Project Leader
> ___
> devel mailing list -- devel@lists.fedoraproject.org
> To unsubscribe send an email to devel-le...@lists.fedoraproject.org
> Fedora Code of Conduct:
> https://docs.fedoraproject.org/en-US/project/code-of-conduct/
> List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
> List Archives:
> https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
> Do not reply to spam, report it:
> https://pagure.io/fedora-infrastructure/new_issue
>
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

[Spectacle] [Bug 465010] Auto copy to clipboard does not work if rectangle is used

[Geraldo Simião]

https://bugs.kde.org/show_bug.cgi?id=465010

--- Comment #5 from Geraldo Simião  ---
But this bug doesn't happens when I'm on X11 (xorg) session.

-- 
You are receiving this mail because:
You are watching all bug changes.

[Spectacle] [Bug 465010] Auto copy to clipboard does not work if rectangle is used

[Geraldo Simião]

https://bugs.kde.org/show_bug.cgi?id=465010

Geraldo Simião  changed:

   What|Removed |Added

 CC||geraldo.simiao.kutz@gmail.c
   ||om

--- Comment #4 from Geraldo Simião  ---
Exactly the same behavior happening here. 

Operating System: Fedora Linux 37
KDE Plasma Version: 5.26.90
KDE Frameworks Version: 5.102.0
Qt Version: 5.15.8
Kernel Version: 6.1.9-200.fc37.x86_64 (64-bit)
Graphics Platform: Wayland
Processors: 8 × Intel® Core™ i7-3632QM CPU @ 2.20GHz
Memory: 15.4 GiB of RAM
Graphics Processor: Mesa Intel® HD Graphics 4000
Manufacturer: Acer

-- 
You are receiving this mail because:
You are watching all bug changes.

[plasmashell] [Bug 464628] Panel size ( width / height ) keeps getting reset after plasmashell restart in Plasma 5.27 beta

[Geraldo Simião]

https://bugs.kde.org/show_bug.cgi?id=464628

Geraldo Simião  changed:

   What|Removed |Added

 CC||geraldo.simiao.kutz@gmail.c
   ||om

--- Comment #1 from Geraldo Simião  ---
I'm seeing this behavior too, but for me it doesn't go to some default height,
it comes back to the size I was using when made the upgrade (38 px). So I
change it to 40 or 42, and when plasma restart its goes back to 38.

#
Operating System: Fedora Linux 37
KDE Plasma Version: 5.26.90
KDE Frameworks Version: 5.102.0
Qt Version: 5.15.8
Kernel Version: 6.1.7-200.fc37.x86_64 (64-bit)
Graphics Platform: Wayland
Processors: 8 × Intel® Core™ i7-3632QM CPU @ 2.20GHz
Memory: 15.4 GiB of RAM
Graphics Processor: Mesa Intel® HD Graphics 4000
Manufacturer: Acer
Product Name: Aspire V3-571

##
WAYLAND info:
interface: 'wl_compositor',  version:  5, name:  1
interface: 'zwp_tablet_manager_v2',  version:  1, name:  3
interface: 'zwp_keyboard_shortcuts_inhibit_manager_v1',  version:  1, name:  4
interface: 'xdg_wm_base',version:  4, name:  6
interface: 'zwlr_layer_shell_v1',version:  3, name:  7
interface: 'zxdg_decoration_manager_v1', version:  1, name:  8
interface: 'wp_viewporter',  version:  1, name:  9
interface: 'wp_fractional_scale_manager_v1', version:  1, name: 10
interface: 'wl_shm', version:  1, name: 11
formats: 'XB48'(0x38344258) 'AB48'(0x38344241) 'XB30'(0x30334258)
'AB30'(0x30334241) 'XR30'(0x30335258) 'AR30'(0x30335241) XRGB ARGB
interface: 'wl_seat',version:  8, name: 12
name: 
capabilities: pointer keyboard touch
keyboard repeat rate: 25
keyboard repeat delay: 449
interface: 'zwp_pointer_gestures_v1',version:  3, name: 13
interface: 'zwp_pointer_constraints_v1', version:  1, name: 14
interface: 'zwp_relative_pointer_manager_v1',version:  1, name: 15
interface: 'wl_data_device_manager', version:  3, name: 16
interface: 'zwlr_data_control_manager_v1',   version:  2, name: 17
interface: 'zwp_primary_selection_device_manager_v1',version:  1, name: 18
interface: 'org_kde_kwin_idle',  version:  1, name: 19
interface: 'zwp_idle_inhibit_manager_v1',version:  1, name: 20
interface: 'ext_idle_notifier_v1',   version:  1, name: 21
interface: 'org_kde_plasma_shell',   version:  8, name: 22
interface: 'org_kde_kwin_appmenu_manager',   version:  1, name: 23
interface: 'org_kde_kwin_server_decoration_palette_manager', version:  1, name:
24
interface: 'org_kde_plasma_virtual_desktop_management',  version:  2, name: 26
interface: 'org_kde_kwin_shadow_manager',version:  2, name: 28
interface: 'org_kde_kwin_dpms_manager',  version:  1, name: 29
interface: 'org_kde_kwin_server_decoration_manager', version:  1, name: 30
interface: 'kde_output_management_v2',   version:  3, name: 31
interface: 'zxdg_output_manager_v1', version:  3, name: 32
xdg_output_v1
output: 49
name: 'HDMI-A-1'
description: 'AOC 24B1W1G5/AVRM4XA00052'
logical_x: 1366, logical_y: 0
logical_width: 1920, logical_height: 1080
xdg_output_v1
output: 48
name: 'LVDS-1'
description: 'LG Display LVDS-1-LP156WH2-TLA'
logical_x: 0, logical_y: 312
logical_width: 1366, logical_height: 768
interface: 'wl_subcompositor',   version:  1, name: 33
interface: 'zxdg_exporter_v2',   version:  1, name: 34
interface: 'zxdg_importer_v2',   version:  1, name: 35
interface: 'xdg_activation_v1',  version:  1, name: 38
interface: 'wp_content_type_manager_v1', version:  1, name: 40
interface: 'wp_tearing_control_manager_v1',  version:  1, name: 41
interface: 'wl_drm', version:  2, name: 43
interface: 'zwp_linux_dmabuf_v1',version:  4, name: 44
formats:
'AR30'(0x30335241), modifier: 0x0102
'AR30'(0x30335241), modifier: 0x0101
'AR30'(0x30335241), modifier: 0x
'Y412'(0x32313459), modifier: 0x0102
'Y412'(0x32313459), modifier: 0x0101
'Y412'(0x32313459), modifier

Re: Cannot reach Bugzilla

[Geraldo Simião Kutz]

Here I can access Bugzilla without problems.

Em sáb, 12 de nov de 2022 09:36, Onyeibo Oku 
escreveu:

> Greetings everyone,
>
> Is it just me or is Bugzilla offline?  I have been trying that site for
> the past
> 2 hours.  What's happening?
>
> Regards
> Onyeibo
> ___
> test mailing list -- test@lists.fedoraproject.org
> To unsubscribe send an email to test-le...@lists.fedoraproject.org
> Fedora Code of Conduct:
> https://docs.fedoraproject.org/en-US/project/code-of-conduct/
> List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
> List Archives:
> https://lists.fedoraproject.org/archives/list/test@lists.fedoraproject.org
> Do not reply to spam, report it:
> https://pagure.io/fedora-infrastructure/new_issue
>
___
test mailing list -- test@lists.fedoraproject.org
To unsubscribe send an email to test-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/test@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

Re: [RESEND PATCH v2] drm/bridge: dw-hdmi-i2s: set insert_pcuv bit if hardware supports it

[Geraldo Nascimento]

On Mon, Oct 31, 2022 at 09:20:36AM +0100, Neil Armstrong wrote:
> Hi,
>

Hi Neil and thanks for caring.

> 
> On 17/10/2022 14:04, Geraldo Nascimento wrote:
> > Hi Mark, resending this as it failed to apply in my last submission. Added
> > Neil Armstrong to Cc: as hopefully he will be able to better review this.
> > 
> > Thanks,
> > Geraldo Nascimento
> > 
> > ---
> > 
> > Starting with version 2.10a of Synopsys DesignWare HDMI controller the
> > insert_pcuv bit was introduced. On RK3399pro SoM (Radxa Rock Pi N10),
> > for example, if we neglect to set this bit and proceed to enable hdmi_sound
> > and i2s2 on the device tree there will be extreme clipping of sound
> > output, to the point that music sounds like white noise. Problem
> > could also manifest as just mild cracking depending of HDMI audio
> > implementation of sink. Setting insert_pcuv bit (bit 2 of
> > aud_conf2 Audio Sample register) fixes this.
> 
> 
> I did some research and this insert_pcuv is already present in the 1.40a 
> version
> of the dw-hdmi databook, so I wonder why suddenly this is needed.

Like I told you, I was unaware of this fact, but I have a hunch this bit
was being set to 1 as default before the 2.10a version of dw-hdmi. It
remains to be checked, I see you added Christian Hewitt to the Cc:,
maybe he can use i2cdump or printk() on older Rockchip  hardware, the
Radxa Rock Pi N10 is the only thing from Rockchip I own.

> 
> The insert_pcuv is documented as:
> ---
> When set (1'b1), it enables the insertion of the PCUV (Parity, Channel 
> Status, User
> bit and Validity) bits on the incoming audio stream (support limited to 
> Linear PCM
> audio).
> If disabled, the incomming audio stream must contain the PCUV bits, mapped
> acording to 2.6.4.2 Data Mapping Examples
> 
> 
> 
> What's interesting is this register is only present if thre DW-HDMI IP is 
> configured
> as GPAUD or GDOUBLE, meaning it must have GPAUD enabled. So it has
> something to do with it, so what's value of it when GPAUD isn't present in 
> the IP ?

Would you like me to inject some printk() or dump some memory value
with i2cdump? I'm not sure I follow you because you obviously know much
more about this driver than me, but if you could elaborate a bit I'd be
happy to provide some answers.

> 
> And HDMI2 spec added this, even PCVU were required before:
> 
> Note that PCUV refers to the parity bit (P), channel status (C), user data 
> (U), and validity bit (V) as defined in IEC
> 60958-1.
> 
> 
> So it has something to do with IEC60958-1 stream format, do maybe this
> insert_pcuv should only be enforced when the input stream is _not_ IEC60958-1 
> ?

Yes, the HDMI2 spec requires PCUV audio bits, and they borrow the idea
from IEC 60958-1 (Digital Audio Interface - DAI), but insert_pcuv definitely
needs to be set for newer Synopsys Designware HDMI hardware when we're
talking about Linear PCM - that's what my patch attempts to address.

Thanks,
Geraldo Nascimento

> 
> Neil
> 
> > 
> > Signed-off-by: Geraldo Nascimento 
> > 
> > ---
> > 
> > v1->v2: SoC->SoM on description, better commenting, minor style changes,
> > conditional application of fix for L-PCM only
> > 
> > --- a/drivers/gpu/drm/bridge/synopsys/dw-hdmi-i2s-audio-20221017.c
> > +++ b/drivers/gpu/drm/bridge/synopsys/dw-hdmi-i2s-audio-20221017.c
> > @@ -42,6 +42,7 @@ static int dw_hdmi_i2s_hw_params(struct device *dev, void 
> > *data,
> > struct dw_hdmi *hdmi = audio->hdmi;
> > u8 conf0 = 0;
> > u8 conf1 = 0;
> > +   u8 conf2 = 0;
> > u8 inputclkfs = 0;
> >   
> > /* it cares I2S only */
> > @@ -101,6 +102,28 @@ static int dw_hdmi_i2s_hw_params(struct device *dev, 
> > void *data,
> > return -EINVAL;
> > }
> >   
> > +   /*
> > +* dw-hdmi introduced insert_pcuv bit in
> > +* version 2.10a.
> > +*
> > +* This single bit (bit 2 of HDMI_AUD_CONF2)
> > +* when set to 1 will enable the insertion of the PCUV
> > +* (Parity, Channel Status, User bit and Validity)
> > +* bits on the incoming audio stream.
> > +*
> > +* Support is limited to Linear PCM audio. If
> > +* neglected, the lack of valid PCUV bits
> > +* on L-PCM streams will cause anything from
> > +* mild cracking to full blown extreme
> > +* clipping depending on the HDMI audio
> > +   

Re: Proposal: make meetings officially every other week

[Geraldo Simião Kutz]

+1 for te proposal.


geraldosimiao

Em seg, 31 de out de 2022 07:19, Kamil Paral  escreveu:

> On Sat, Oct 29, 2022 at 2:49 AM Adam Williamson <
> adamw...@fedoraproject.org> wrote:
>
>> Anyway, it seems a bit silly that we still notionally schedule a
>> meeting every week but I almost always cancel half of them. So I'm
>> proposing we make it official that we only meet every *other* week.
>> This would save sending out cancellation notices and manually canceling
>> the event in the calendar every other week.
>>
>
> +1, every other week is fine
>
> ___
> test mailing list -- test@lists.fedoraproject.org
> To unsubscribe send an email to test-le...@lists.fedoraproject.org
> Fedora Code of Conduct:
> https://docs.fedoraproject.org/en-US/project/code-of-conduct/
> List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
> List Archives:
> https://lists.fedoraproject.org/archives/list/test@lists.fedoraproject.org
> Do not reply to spam, report it:
> https://pagure.io/fedora-infrastructure/new_issue
>
___
test mailing list -- test@lists.fedoraproject.org
To unsubscribe send an email to test-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/test@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

[RESEND PATCH v2] drm/bridge: dw-hdmi-i2s: set insert_pcuv bit if hardware supports it

[Geraldo Nascimento]

Hi Mark, resending this as it failed to apply in my last submission. Added
Neil Armstrong to Cc: as hopefully he will be able to better review this.

Thanks,
Geraldo Nascimento

---

Starting with version 2.10a of Synopsys DesignWare HDMI controller the
insert_pcuv bit was introduced. On RK3399pro SoM (Radxa Rock Pi N10),
for example, if we neglect to set this bit and proceed to enable hdmi_sound
and i2s2 on the device tree there will be extreme clipping of sound
output, to the point that music sounds like white noise. Problem
could also manifest as just mild cracking depending of HDMI audio
implementation of sink. Setting insert_pcuv bit (bit 2 of
aud_conf2 Audio Sample register) fixes this.

Signed-off-by: Geraldo Nascimento 

---

v1->v2: SoC->SoM on description, better commenting, minor style changes,
conditional application of fix for L-PCM only

--- a/drivers/gpu/drm/bridge/synopsys/dw-hdmi-i2s-audio-20221017.c
+++ b/drivers/gpu/drm/bridge/synopsys/dw-hdmi-i2s-audio-20221017.c
@@ -42,6 +42,7 @@ static int dw_hdmi_i2s_hw_params(struct device *dev, void 
*data,
struct dw_hdmi *hdmi = audio->hdmi;
u8 conf0 = 0;
u8 conf1 = 0;
+   u8 conf2 = 0;
u8 inputclkfs = 0;
 
/* it cares I2S only */
@@ -101,6 +102,28 @@ static int dw_hdmi_i2s_hw_params(struct device *dev, void 
*data,
return -EINVAL;
}
 
+   /*
+* dw-hdmi introduced insert_pcuv bit in
+* version 2.10a.
+*
+* This single bit (bit 2 of HDMI_AUD_CONF2)
+* when set to 1 will enable the insertion of the PCUV
+* (Parity, Channel Status, User bit and Validity)
+* bits on the incoming audio stream.
+* 
+* Support is limited to Linear PCM audio. If
+* neglected, the lack of valid PCUV bits
+* on L-PCM streams will cause anything from
+* mild cracking to full blown extreme
+* clipping depending on the HDMI audio
+* implementation of the sink.
+*
+*/
+
+   if (hdmi_read(audio, HDMI_DESIGN_ID) >= 0x21 &&
+   !(hparms->iec.status[0] & IEC958_AES0_NONAUDIO))
+   conf2 = HDMI_AUD_CONF2_INSERT_PCUV;
+
dw_hdmi_set_sample_rate(hdmi, hparms->sample_rate);
dw_hdmi_set_channel_status(hdmi, hparms->iec.status);
dw_hdmi_set_channel_count(hdmi, hparms->channels);
@@ -109,6 +120,7 @@ static int dw_hdmi_i2s_hw_params(struct device *dev, void 
*data,
hdmi_write(audio, inputclkfs, HDMI_AUD_INPUTCLKFS);
hdmi_write(audio, conf0, HDMI_AUD_CONF0);
hdmi_write(audio, conf1, HDMI_AUD_CONF1);
+   hdmi_write(audio, conf2, HDMI_AUD_CONF2);
 
return 0;
 }
--- a/drivers/gpu/drm/bridge/synopsys/dw-hdmi-20221017.h
+++ b/drivers/gpu/drm/bridge/synopsys/dw-hdmi-20221017.h
@@ -931,6 +931,11 @@ enum {
HDMI_AUD_CONF1_WIDTH_16 = 0x10,
HDMI_AUD_CONF1_WIDTH_24 = 0x18,
 
+/* AUD_CONF2 field values */
+   HDMI_AUD_CONF2_HBR = 0x01,
+   HDMI_AUD_CONF2_NLPCM = 0x02,
+   HDMI_AUD_CONF2_INSERT_PCUV = 0x04,
+
 /* AUD_CTS3 field values */
HDMI_AUD_CTS3_N_SHIFT_OFFSET = 5,
HDMI_AUD_CTS3_N_SHIFT_MASK = 0xe0,

Re: Grub menu with 3 kernels by default

[Geraldo Simião Kutz]

On my acer Aspire laptop it's the "esc" key. Works everytime I want to see
the grub menu.

geraldosimiao

Em qua, 5 de out de 2022 12:33, Chris Murphy 
escreveu:

>
>
> On Wed, Oct 5, 2022, at 11:16 AM, Christopher Klooz wrote:
>
> > However, on ask.fp, a user mentioned that the grub menu is no longer
> > enabled by default on single boot systems so that changing the kernel is
> > no longer easily possible, and put forward
> > https://fedoraproject.org/wiki/Changes/HiddenGrubMenu as evidence for
> > this argument. Yet, the article indicates that the argument is not fully
> > correct and even with single boot installations, SHIFT can be used to
> > get into the grub menu.
>
> I think it's F8 or SHIFT. F8 doesn't work on many laptops I've found,
> because it's reserved by UEFI firmware for one of its menus. And SHIFT has
> never worked. Maybe Esc or TAB?
>
> Given this inconsistency, I have a mixed opinion of the hidden GRUB menu.
>
>
> --
> Chris Murphy
> ___
> devel mailing list -- devel@lists.fedoraproject.org
> To unsubscribe send an email to devel-le...@lists.fedoraproject.org
> Fedora Code of Conduct:
> https://docs.fedoraproject.org/en-US/project/code-of-conduct/
> List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
> List Archives:
> https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
> Do not reply to spam, report it:
> https://pagure.io/fedora-infrastructure/new_issue
>
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

Re: Call for testing: UEFI boot of current Rawhide images written to USB with dd

[Geraldo Simião Kutz]

Adam, I tested with this same iso you linked here on two different
computers (acer aspire native UEFI and HP-G42 BIOS) pendrive (Sandisk
cruzer blade 16GB) using dd (dd
if="./Fedora-Everything-netinst-x86_64-Rawhide-20220802.n.0.iso"
of="/dev/sdb" status="progress" conv="fsync").
Both booted fine to the installer, no problems here.
Hope this helps.

Geraldo

@geraldosimiao:matrix.org


Em ter., 2 de ago. de 2022 às 20:44, Adam Williamson <
adamw...@fedoraproject.org> escreveu:

> Hey folks!
>
> As part of testing the switch to using grub2 for BIOS boot of live and
> installer images, I tried writing a recent image to USB with dd and
> booting it in native UEFI mode on my test box. It didn't work.
>
> However, Brian Lane says it's fine for him, and I haven't seen anyone
> else mention this issue. So maybe it's something odd with my test stick
> or system.
>
> Can anyone else try writing a recent Rawhide image - I used Fedora-
> Everything-netinst-x86_64-Rawhide-20220704.n.0.iso at the time, so a
> current equivalent would be
>
> https://kojipkgs.fedoraproject.org/compose/rawhide/Fedora-Rawhide-20220802.n.0/compose/Everything/x86_64/iso/Fedora-Everything-netinst-x86_64-Rawhide-20220802.n.0.iso
> - to USB with dd then booting it in native UEFI mode on some system,
> and see if it works? It'd be good to know if there's a general issue or
> I just have some cranky hardware. Thanks!
> --
> Adam Williamson
> Fedora QA
> IRC: adamw | Twitter: adamw_ha
> https://www.happyassassin.net
>
> ___
> test mailing list -- test@lists.fedoraproject.org
> To unsubscribe send an email to test-le...@lists.fedoraproject.org
> Fedora Code of Conduct:
> https://docs.fedoraproject.org/en-US/project/code-of-conduct/
> List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
> List Archives:
> https://lists.fedoraproject.org/archives/list/test@lists.fedoraproject.org
> Do not reply to spam, report it:
> https://pagure.io/fedora-infrastructure/new_issue
>
___
test mailing list -- test@lists.fedoraproject.org
To unsubscribe send an email to test-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/test@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

Re: [dspace-tech] Tranferindo arquivos

[José Geraldo]

Boa tarde,

Sim, faz o backup do banco e do diretório assetstore.

Esse link pode auxilia-los:
https://wiki.lyrasis.org/display/DSDOC6x/Upgrading+DSpace


Em qua., 29 de jun. de 2022 às 11:28, FASIPE SUPORTE <
fasipesupo...@gmail.com> escreveu:

> I ask for help please. I have DSpace 5.1 installed but I need to transfer
> to another server, I installed 6.3, can I transfer all data to the new one?
> Is there a folder I can transfer that will take advantage of all the
> published articles as well as the description of each one? Thank you very
> much in advance.
>
> --
> All messages to this mailing list should adhere to the Code of Conduct:
> https://www.lyrasis.org/about/Pages/Code-of-Conduct.aspx
> ---
> You received this message because you are subscribed to the Google Groups
> "DSpace Technical Support" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to dspace-tech+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/dspace-tech/98c57430-16a6-4fce-af73-f071a609c48bn%40googlegroups.com
> <https://groups.google.com/d/msgid/dspace-tech/98c57430-16a6-4fce-af73-f071a609c48bn%40googlegroups.com?utm_medium=email_source=footer>
> .
>


-- 
At.te,

José Geraldo

-- 
All messages to this mailing list should adhere to the Code of Conduct: 
https://www.lyrasis.org/about/Pages/Code-of-Conduct.aspx
--- 
You received this message because you are subscribed to the Google Groups 
"DSpace Technical Support" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to dspace-tech+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/dspace-tech/CANP4ikTy4BaVurmdsEVK-yUGhjT6hG7wJe87Y4NO5CUWQHrHFw%40mail.gmail.com.

Re: Please help us test: Fedora Media Writer 5.0

[Geraldo Simião Kutz]

Ok, thanks Kamil

Em ter, 10 de mai de 2022 02:20, Kamil Paral  escreveu:

> On Thu, May 5, 2022 at 7:05 PM Kamil Paral  wrote:
>
>> Hi there. We just learned that there's an opportunity to have a brand new
>> Fedora Media Writer 5.0 (with a completely redone UI, but using the same
>> background code) together with the Fedora 36 release. The timing is tight,
>> but we agreed that we'd like to give it a try.
>>
>
> Thanks everyone for testing! I believe this has been super-helpful and we
> uncovered (and Jan fixed) lots of issues. FMW 5.0 should be available
> officially today together with Fedora 36 (if stars align, otherwise a few
> days later). Testing the latest builds (from the project page or from
> updates-testing) is of course still very useful. If you find any more
> bugs/issues, please report them at
> https://github.com/FedoraQt/MediaWriter/issues (instead of this mailing
> list). Thank you!
>
> ___
> test mailing list -- test@lists.fedoraproject.org
> To unsubscribe send an email to test-le...@lists.fedoraproject.org
> Fedora Code of Conduct:
> https://docs.fedoraproject.org/en-US/project/code-of-conduct/
> List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
> List Archives:
> https://lists.fedoraproject.org/archives/list/test@lists.fedoraproject.org
> Do not reply to spam on the list, report it:
> https://pagure.io/fedora-infrastructure
>
___
test mailing list -- test@lists.fedoraproject.org
To unsubscribe send an email to test-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/test@lists.fedoraproject.org
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure

Re: Please help us test: Fedora Media Writer 5.0

[Geraldo Simião Kutz]

allright, with 5.0 PT-br is almost done (Rafael tod me he finished by now).

I saw strange alignment of progress numbers at this window. attached

Em seg., 9 de mai. de 2022 às 22:54, Geraldo Simião Kutz <
geraldo.simiao.k...@gmail.com> escreveu:

> Working fine here. Tested the RPM (4.9.99-4.fc36.rpm)
> Only missed the PT_BR translations.
>
> Em seg., 9 de mai. de 2022 às 04:23, Luna Jernberg 
> escreveu:
>
>> Hey!
>>
>> Working on updating the Swedish translation now (while attending Red Hat
>> Summit Online 2022)
>>
>> On Fri, May 6, 2022 at 5:47 PM Jan Grulich  wrote:
>>
>>> Alright, I believe this was very useful as we fixed countless issues
>>> today. Thank you all who participated.
>>>
>>> Here is latest scratch build for the weekend testers:
>>> https://koji.fedoraproject.org/koji/taskinfo?taskID=86732788
>>> And other builds can be found here:
>>> https://github.com/FedoraQt/MediaWriter/releases
>>>
>>> I will take a break now as today was quite exhausting :).
>>> ___
>>> test mailing list -- test@lists.fedoraproject.org
>>> To unsubscribe send an email to test-le...@lists.fedoraproject.org
>>> Fedora Code of Conduct:
>>> https://docs.fedoraproject.org/en-US/project/code-of-conduct/
>>> List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
>>> List Archives:
>>> https://lists.fedoraproject.org/archives/list/test@lists.fedoraproject.org
>>> Do not reply to spam on the list, report it:
>>> https://pagure.io/fedora-infrastructure
>>>
>> ___
>> test mailing list -- test@lists.fedoraproject.org
>> To unsubscribe send an email to test-le...@lists.fedoraproject.org
>> Fedora Code of Conduct:
>> https://docs.fedoraproject.org/en-US/project/code-of-conduct/
>> List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
>> List Archives:
>> https://lists.fedoraproject.org/archives/list/test@lists.fedoraproject.org
>> Do not reply to spam on the list, report it:
>> https://pagure.io/fedora-infrastructure
>>
>
___
test mailing list -- test@lists.fedoraproject.org
To unsubscribe send an email to test-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/test@lists.fedoraproject.org
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure

Re: Please help us test: Fedora Media Writer 5.0

[Geraldo Simião Kutz]

Working fine here. Tested the RPM (4.9.99-4.fc36.rpm)
Only missed the PT_BR translations.

Em seg., 9 de mai. de 2022 às 04:23, Luna Jernberg 
escreveu:

> Hey!
>
> Working on updating the Swedish translation now (while attending Red Hat
> Summit Online 2022)
>
> On Fri, May 6, 2022 at 5:47 PM Jan Grulich  wrote:
>
>> Alright, I believe this was very useful as we fixed countless issues
>> today. Thank you all who participated.
>>
>> Here is latest scratch build for the weekend testers:
>> https://koji.fedoraproject.org/koji/taskinfo?taskID=86732788
>> And other builds can be found here:
>> https://github.com/FedoraQt/MediaWriter/releases
>>
>> I will take a break now as today was quite exhausting :).
>> ___
>> test mailing list -- test@lists.fedoraproject.org
>> To unsubscribe send an email to test-le...@lists.fedoraproject.org
>> Fedora Code of Conduct:
>> https://docs.fedoraproject.org/en-US/project/code-of-conduct/
>> List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
>> List Archives:
>> https://lists.fedoraproject.org/archives/list/test@lists.fedoraproject.org
>> Do not reply to spam on the list, report it:
>> https://pagure.io/fedora-infrastructure
>>
> ___
> test mailing list -- test@lists.fedoraproject.org
> To unsubscribe send an email to test-le...@lists.fedoraproject.org
> Fedora Code of Conduct:
> https://docs.fedoraproject.org/en-US/project/code-of-conduct/
> List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
> List Archives:
> https://lists.fedoraproject.org/archives/list/test@lists.fedoraproject.org
> Do not reply to spam on the list, report it:
> https://pagure.io/fedora-infrastructure
>
___
test mailing list -- test@lists.fedoraproject.org
To unsubscribe send an email to test-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/test@lists.fedoraproject.org
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure

Re: grub2 BIOS booting iso and code

[Geraldo Simião Kutz]

Tested this iso with an USB stick on this machine here and it passed the
tests and Anaconda started correctly.

Machine: Type: Laptop System: Hewlett-Packard product: HP G42 Notebook PC
Mobo: Hewlett-Packard model: 1484 v: 77.19 BIOS: Hewlett-Packard v: F.17
date: 07/06/2010
CPU Dual core Pentium T4500 2.3GHz
RAM 6GB

Geraldo Simião

@geraldosimiao:matrix.org

Em seg, 18 de abr de 2022 14:44, Thomas Schmitt 
escreveu:

> Hi,
>
> i wrote:
> > > xorrisofs option --mbr-force-bootable
>
> Chris Murphy wrote:
> > with the bit set it means older versions of
> > Tianocore or anything based on Tianocore up until maybe 6 months ago,
> > won't boot.
>
> Is this maybe about the code snippet of Tianocore which Alexander E.
> Patrakov showed in the course of the grub-bug thread of 2015/16 ?
>
>   https://marc.info/?l=grub-bug=145052969801875=2
>   "
>   OK, Tiano Core validates the protective partition as follows:
>
>   //
>   // Verify that the Protective MBR is valid
>   //
>   for (Index = 0; Index < MAX_MBR_PARTITIONS; Index++) {
> if (ProtectiveMbr->Partition[Index].BootIndicator == 0x00 &&
> ProtectiveMbr->Partition[Index].OSIndicator == PMBR_GPT_PARTITION
> &&
> UNPACK_UINT32 (ProtectiveMbr->Partition[Index].StartingLBA) == 1
> ) {
>   break;
> }
>   }
>   if (Index == MAX_MBR_PARTITIONS) {
> goto Done;  // i.e. not valid
>   }
>
>   So here is an alternative suggestion: don't mark the protective
> partition,
>   create another dummy MBR partition of type 0x00, mark it as bootable.
>   "
>
> That's what --mbr-force-bootable does.
> The shown code will find type 0xEE == PMBR_GPT_PARTITION in partition 1
> with boot/active flag == 0x00 and be happy.
>
> Others which are more picky will hopefully ignore partitions of type 0x00.
> UEFI 2.8 , 5.2.1 Legacy Master Boot Record (MBR) says:
>   "The following test must be performed to determine if a legacy MBR is
>valid:
>* The Signature must be 0xaa55.
>* A Partition Record that contains an OSType value of zero or a
>  SizeInLBA value of zero may be ignored."
>
> For now, "may be ignored" seems to be enough of protection against trouble.
>
>
> An alternative to --mbr-force-bootable could be to offer a 16-byte file
> for download together with the instructions to patch it into a pure and
> specs conformant ISO with GPT. Of course, only if a 10 year old laptop
> refuses to recognize the original ISO on USB stick.
>
> The bytes would have to be
>
>   { 128, 0, 1, 0, 0, 0, 1, 0, 0, 0, 0, 0, 1, 0, 0, 0 }
>
> Assumed the file is named "dummy_mbr_part2.img" the patch instruction
> would be
>
>dd if=dummy_mbr_part2.img of=boot-grub2-f36.iso \
>   conv=notrunc bs=1 seek=462 count=16
>
> -
>
> Ubuntu is testing this for you since about a year. :))
>
> Afaik the first official ISO of this layout was
>   ubuntu-21.04-desktop-amd64.iso
> and they did _not_ revoke it half a year later with
>   ubuntu-21.10-desktop-amd64.iso
>
>   $ xorriso -indev ubuntu-21.10-desktop-amd64.iso -report_system_area plain
>   ...
>   Volume id: 'Ubuntu 21.10 amd64'
>   System area options: 0x4201
>   System area summary: MBR protective-msdos-label grub2-mbr cyl-align-off
> GPT
>   ISO image size/512 : 6086880
>   Partition offset   : 16
>   MBR heads per cyl  : 0
>   MBR secs per head  : 0
>   MBR partition table:   N Status  TypeStart   Blocks
>   MBR partition  :   1   0x00  0xee1  6086879
>   MBR partition  :   2   0x80  0x0001
>   GPT:   N  Info
>   ...
>
>   $ /sbin/fdisk -l ubuntu-21.10-desktop-amd64.iso
>
>   Disk ubuntu-21.10-desktop-amd64.iso: 2.9 GiB, 3116482560 bytes, 6086880
> sectors
>   Units: sectors of 1 * 512 = 512 bytes
>   Sector size (logical/physical): 512 bytes / 512 bytes
>   I/O size (minimum/optimal): 512 bytes / 512 bytes
>   Disklabel type: gpt
>   Disk identifier: EF83665C-2F29-48D6-8C3F-80F5A69CFEB7
>
>   DeviceStart End Sectors  Size Type
>   ubuntu-21.10-desktop-amd64.iso1  64 6077751 6077688  2.9G Microsoft
> basic da
>   ubuntu-21.10-desktop-amd64.iso2 6077752 60862158464  4.1M EFI System
>   ubuntu-21.10-desktop-amd64.iso3 6086216 6086815 600  300K Microsoft
> basic da
>
> -
>
> Whatever, we do not yet know for sure whether the boot failure with the
> Dell XPS 15 L502X is caused by the lack of a boot/active flag.
&

Re: Problem: package lilv-0.24.12-4.fc37.x86_64 obsoletes lilv < 0.24.12-2 provided by lilv-0.24.12-1.fc36.i686

[Geraldo Simião Kutz]

Seems that one is having issues in f36 too
https://bugzilla.redhat.com/show_bug.cgi?id=2052588

Em dom, 17 de abr de 2022 15:59, Kamil Paral  escreveu:

> On Fri, Apr 15, 2022 at 12:54 AM Reon Beon via test <
> test@lists.fedoraproject.org> wrote:
>
>> Fedora rawhide openh264 (From Cisco) - x86_64   1.7 kB/s
>> | 989  B 00:00
>> Fedora - Rawhide - Developmental packages for the next Fedora r  27 kB/s
>> |  12 kB 00:00
>> Fedora - Modular Rawhide - Developmental packages for the next   28 kB/s
>> |  12 kB 00:00
>> RPM Fusion for Fedora Rawhide - Free 12 kB/s
>> | 6.7 kB 00:00
>> RPM Fusion for Fedora Rawhide - Nonfree  16 kB/s
>> | 6.8 kB 00:00
>> RPM Fusion for Fedora rawhide - Nonfree - Steam  13 kB/s
>> | 5.5 kB 00:00
>> Dependencies resolved.
>>
>>  Problem: package lilv-0.24.12-4.fc37.x86_64 obsoletes lilv < 0.24.12-2
>> provided by lilv-0.24.12-1.fc36.i686
>>   - cannot install the best update candidate for package
>> lilv-0.24.12-1.fc36.x86_64
>>   - problem with installed package lilv-0.24.12-1.fc36.i686
>>
>
> Please report this problem against the lilv package into bugzilla, thank
> you.
>
> ___
> test mailing list -- test@lists.fedoraproject.org
> To unsubscribe send an email to test-le...@lists.fedoraproject.org
> Fedora Code of Conduct:
> https://docs.fedoraproject.org/en-US/project/code-of-conduct/
> List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
> List Archives:
> https://lists.fedoraproject.org/archives/list/test@lists.fedoraproject.org
> Do not reply to spam on the list, report it:
> https://pagure.io/fedora-infrastructure
>
___
test mailing list -- test@lists.fedoraproject.org
To unsubscribe send an email to test-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/test@lists.fedoraproject.org
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure

[kwin] [Bug 427060] Cursor "hit box" is offset under Wayland on VMs (VMWare, VirtualBox, ...)

[Geraldo Simião]

https://bugs.kde.org/show_bug.cgi?id=427060

Geraldo Simião  changed:

   What|Removed |Added

 CC||geraldo.simiao.kutz@gmail.c
   ||om

--- Comment #30 from Geraldo Simião  ---
(In reply to Adam Williamson from comment #28)
> From my perspective it seems like this got fixed, then came back. In Fedora
> 35 we were suffering from this; I backported
> https://github.com/KDE/kwin/commit/
> 998bbf4eba724a9b94a5bae62182456b85b11383#diff-
> 034885748897f413c645e3efd125d7c0db9a8454d580f6093e40c885d974c818 , and that
> fixed it. Now people are reporting in F36 Beta that it's back again.
> 
> What changed upstream? Was that fix reverted or lost?

Just opened a new RHBZ ticket:
https://bugzilla.redhat.com/show_bug.cgi?id=2063969

-- 
You are receiving this mail because:
You are watching all bug changes.

[Discover] [Bug 448460] discover 5.23.90 crashes with segfault on startup

[Geraldo Simião]

https://bugs.kde.org/show_bug.cgi?id=448460

--- Comment #27 from Geraldo Simião  ---
I can confirm here, fixed in 5.24.0

-- 
You are receiving this mail because:
You are watching all bug changes.

[Discover] [Bug 448460] discover 5.23.90 crashes with segfault on startup

[Geraldo Simião]

https://bugs.kde.org/show_bug.cgi?id=448460

--- Comment #17 from Geraldo Simião  ---
Confirmed that here too, on fedora 35.

Operating System: Fedora Linux 35
KDE Plasma Version: 5.23.90
KDE Frameworks Version: 5.90.0
Qt Version: 5.15.2
Kernel Version: 5.16.1-200.fc35.x86_64 (64-bit)

-- 
You are receiving this mail because:
You are watching all bug changes.

[Discover] [Bug 448460] discover 5.23.90 crashes with segfault on startup

[Geraldo Simião]

https://bugs.kde.org/show_bug.cgi?id=448460

Geraldo Simião  changed:

   What|Removed |Added

 CC||geraldo.simiao.kutz@gmail.c
   ||om

--- Comment #16 from Geraldo Simião  ---
Created attachment 145609
  --> https://bugs.kde.org/attachment.cgi?id=145609=edit
journactl -f from the moment discover started until it crashed

-- 
You are receiving this mail because:
You are watching all bug changes.

[id-android] WTA: Smartphone dengan wide lens dan Pengambilan video bagus

[Georgeus Geraldo]

Dear All,

Sedang dicari smartphone dengan kamera wide untuk pengambilan video Yoga.
Kira2 yang bagus apa ya? Budget max di 3.5jt

Tolong dibantu sarannya ya. Thankyou
-- 
@gregeorgeraldo on Graphite Mini

-- 
===
Ayo Subscribe >>  Channel YouTube
https://www.youtube.com/user/komunitasandroid

--
Kontak Admin: 
IG   https://www.instagram.com/agushamonangan

---
FB Groups :  https://www.facebook.com/groups/android.or.id

Aturan Umum  ID-ANDROID >> goo.gl/mL1mBT

==
--- 
Anda menerima pesan ini karena Anda berlangganan grup "[id-android] Indonesian 
Android Community" dari Google Grup.
Untuk berhenti berlangganan dan berhenti menerima email dari grup ini, kirim 
email ke id-android+unsubscr...@googlegroups.com.
Untuk melihat diskusi ini di web, kunjungi 
https://groups.google.com/d/msgid/id-android/CAK650917-y4z9ckzsGLCLpJiXuOdiBZ36KfM%3DKwWKR6mVjG2SQ%40mail.gmail.com.

[plasmashell] [Bug 437455] Plasma crashed on Wayland in QWaylandClientExtensionPrivate::handleRegistryGlobal() when enabling blur effect in Desktop Effects KCM

[Geraldo Simião]

https://bugs.kde.org/show_bug.cgi?id=437455

Geraldo Simião  changed:

   What|Removed |Added

 CC||geraldo.simiao.kutz@gmail.c
   ||om

-- 
You are receiving this mail because:
You are watching all bug changes.

[plasmashell] [Bug 437455] Plasma crashed on Wayland in QWaylandClientExtensionPrivate::handleRegistryGlobal() when enabling blur effect in Desktop Effects KCM

[Geraldo Simião]

https://bugs.kde.org/show_bug.cgi?id=437455

--- Comment #35 from Geraldo Simião  ---
Created attachment 142553
  --> https://bugs.kde.org/attachment.cgi?id=142553=edit
New crash information added by DrKonqi

systemsettings5 (5.22.5) using Qt 5.15.2

- What I was doing when the application crashed:
I deleted one virtual desktop at system settings, saved, and then closed system
settings. At plasma wayland session, Fedora 35.

-- Backtrace (Reduced):
#6  0x7fc98527c6a4 in QWaylandClientExtensionPrivate::handleRegistryGlobal
(data=0x5631c1dd9890, registry=0x5631bf6c41f0, id=47, interface=..., version=1)
at global/qwaylandclientextension.cpp:67
#7  0x7fc9852691b9 in QtWaylandClient::QWaylandDisplay::registry_global
(this=, id=, interface=..., version=) at
/usr/src/debug/qt5-qtwayland-5.15.2-14.fc35.x86_64/src/client/qwaylanddisplay.cpp:397
#8  0x7fc985285af3 in QtWayland::wl_registry::handle_global
(data=0x5631bf6c04b0, object=, name=47, interface=0x5631c205b3c0
"org_kde_kwin_blur_manager", version=1) at
/usr/src/debug/qt5-qtwayland-5.15.2-14.fc35.x86_64/src/client/qwayland-wayland.cpp:94
#9  0x7fc982b1bc04 in ffi_call_unix64 () at ../src/x86/unix64.S:76
#10 0x7fc982b1b108 in ffi_call (cif=cif@entry=0x7ffcab77cd60, fn=, rvalue=, rvalue@entry=0x0,
avalue=avalue@entry=0x7ffcab77ce30) at ../src/x86/ffi64.c:525

-- 
You are receiving this mail because:
You are watching all bug changes.

Re: python3-jwt+crypto and python3-cryptography

[Geraldo Simião Kutz]

Ohh, thanks Miro.
I didn't see that :)

Em ter, 5 de out de 2021 08:21, Miro Hrončok  escreveu:

> On 05. 10. 21 13:13, Geraldo Simião Kutz wrote:
> > Good morning/afternoon everyone,
> >
> > I'm having this dependency problem, is this correct?
> >
> > If i use dnf up --best --allowerasing it will naturally remove
> python3-jwt+crypto
> >
> > Will this be normalyzed by the end of freeze?
> >
> > #
> >   Problema: pacote python3-jwt+crypto-2.1.0-2.fc35.noarch requer
> > (python3.10dist(cryptography) < 4 with python3.10dist(cryptography) >=
> 3.3.1),
> > mas nenhum dos provedores pode ser instalado
> >- não é possível instalar python3-cryptography-35.0.0-2.fc35.x86_64 e
> > python3-cryptography-3.4.7-5.fc35.x86_64
> >- não é possível instalar o melhor candidato à atualização para o
> pacote
> > python3-jwt+crypto-2.1.0-2.fc35.noarch
> >- não é possível instalar o melhor candidato à atualização para o
> pacote
> > python3-cryptography-3.4.7-5.fc35.x86_64
> >
> =
> >   Pacote   Arquitetura
>
> >   VersãoRepositório
>
> >   Tam.
> >
> =
> > Ignorando pacotes com conflitos:
> > (adicionar --best --allowerasing' a linha de comando para forçar sua
> atualização):
> >   python3-cryptography x86_64
>
> > 35.0.0-2.fc35 updates-testing
>   1.0 M
> >
> > Resumo da transação
> >
> =
> > Ignorar  1 Pacote
>
> https://bugzilla.redhat.com/show_bug.cgi?id=2010061
>
> --
> Miro Hrončok
> --
> Phone: +420777974800
> IRC: mhroncok
>
>
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure

python3-jwt+crypto and python3-cryptography

[Geraldo Simião Kutz]

Good morning/afternoon everyone,

I'm having this dependency problem, is this correct?

If i use dnf up --best --allowerasing it will naturally remove
python3-jwt+crypto

Will this be normalyzed by the end of freeze?

#
 Problema: pacote python3-jwt+crypto-2.1.0-2.fc35.noarch requer
(python3.10dist(cryptography) < 4 with python3.10dist(cryptography) >=
3.3.1), mas nenhum dos provedores pode ser instalado
  - não é possível instalar python3-cryptography-35.0.0-2.fc35.x86_64 e
python3-cryptography-3.4.7-5.fc35.x86_64
  - não é possível instalar o melhor candidato à atualização para o pacote
python3-jwt+crypto-2.1.0-2.fc35.noarch
  - não é possível instalar o melhor candidato à atualização para o pacote
python3-cryptography-3.4.7-5.fc35.x86_64
=
 Pacote   Arquitetura
 VersãoRepositório
 Tam.
=
Ignorando pacotes com conflitos:
(adicionar --best --allowerasing' a linha de comando para forçar sua
atualização):
 python3-cryptography x86_64
  35.0.0-2.fc35 updates-testing
1.0 M

Resumo da transação
=
Ignorar  1 Pacote
#

Best regards

Geraldo
geraldosimiao
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure

[kdeconnect] [Bug 442732] crash after abort of upload from android mobile phone to pc

[Geraldo Simião]

https://bugs.kde.org/show_bug.cgi?id=442732

Geraldo Simião  changed:

   What|Removed |Added

 CC||geraldo.simiao.kutz@gmail.c
   ||om

-- 
You are receiving this mail because:
You are watching all bug changes.

[kdeconnect] [Bug 442732] crash after abort of upload from android mobile phone to pc

[Geraldo Simião]

https://bugs.kde.org/show_bug.cgi?id=442732

--- Comment #2 from Geraldo Simião  ---
Created attachment 142151
  --> https://bugs.kde.org/attachment.cgi?id=142151=edit
New crash information added by DrKonqi

kdeconnectd (21.04.3) using Qt 5.15.2

I was copying files to PC and then abort the process

-- Backtrace (Reduced):
#6  KJob::kill (this=0x5643e50010f0, verbosity=KJob::Quietly) at
/usr/src/debug/kf5-kcoreaddons-5.85.0-1.fc35.x86_64/src/lib/jobs/kjob.cpp:108
#7  0x7ff90fdc664c in KJob::kill (this=0x5643e5203540,
verbosity=KJob::EmitResult) at
/usr/src/debug/kf5-kcoreaddons-5.85.0-1.fc35.x86_64/src/lib/jobs/kjob.cpp:112
#8  0x7ff90ecdd3f0 in doActivate (sender=0x5643e4f83380,
signal_index=3, argv=0x7ffc17bd6e50) at kernel/qobject.cpp:3898
#9  0x7ff90e25fd43 in OrgKdeJobViewV2Interface::qt_metacall
(this=0x5643e4f83380, _c=QMetaObject::InvokeMetaMethod, _id=0,
_a=0x7ffc17bd6f90) at
/usr/src/debug/kf5-kjobwidgets-5.85.0-1.fc35.x86_64/redhat-linux-build/src/jobviewiface.moc:212
#10 0x7ff90f5f81eb in QDBusConnectionPrivate::deliverCall (this=, object=, msg=..., metaTypes=..., slotIdx=)
at ../../include/QtCore/../../src/corelib/tools/qvarlengtharray.h:190

-- 
You are receiving this mail because:
You are watching all bug changes.

Re: ALSA kernel projects - for academic purposes

[Geraldo Nascimento]

On Wed, Sep 29, 2021 at 11:07:15AM -0400, Ruben Safir wrote:
> On Fri, Sep 24, 2021 at 07:26:08PM -0300, Geraldo Nascimento wrote:
> > On Fri, Sep 24, 2021 at 10:28:01PM +0530, Muni Sekhar wrote:
> > > On Fri, Sep 24, 2021 at 10:02 PM Valdis Klētnieks
> > >  wrote:
> > > >
> > > > On Fri, 24 Sep 2021 19:34:59 +0530, Muni Sekhar said:
> > > > > What small projects would you suggest to a novice with the ALSA
> > > > > kernel. The aim is to develop a familiarity with the ALSA kernel
> > > > > source code, and also to submit it for academic purposes.
> > 
> > I'm not an academicist by far but if you want your patches to be academic,
> > I think it's more of a question of scientific rigour and scientific
> > method, 
> 
> 
> No - it is an issue of education.  They are trying to learn something
> that they don't already know.  The contribution is they become educated.
>
> > such that when the patch(set) is finally accepted by the Linux
> > community and Linus Torvalds ultimately, you can write a paper about
> > it.
> >
> 
> 
> They are not writing a paper for Linus.  They are writing it for their
> dean or mentor.
>

Hello Ruben,

I don't see your point here. I mentioned not being in academia myself
but last time I was, the academics, from the most junior to the most
seasoned scholar, are writing for journals. They are writing to get
published and cited hopefully.

If they were writing for their dean or mentor to grade them, that would
be called homework. While that's arguably part of education, higher
or otherwise, Muni Sekhar certainly did not ask for help with his
homework.

> 
> > Obviously there are a lot of things an academicist could bring from his
> > background to improve the Linux kernel, 
> 
> Yeah - but that is not what they are trying to do.  And if that was the
> case, this would likely not be the list for it, since this is a newbies
> list.
> 
> 
> > My suggestion is to ask Takashi Iwai if he has in mind 
> 
> BOINK - the doesn't need a new student dragging on his tail and if he
> did then he would chose an intern to help with his code.
> 
> You are failing to understand how higher education works.

I do have my gripes with higher education and I never suggested I
understood it.

As to contacting the maintainer precisely of the part of the kernel you
want to contribute (ALSA kernel-side for Muni Sekhar in this case)
before actually contributing any code, this sounds, at least to me,
like sensible advice.

Thank you,
Geraldo Nascimento

> 
> > ___
> > Kernelnewbies mailing list
> > Kernelnewbies@kernelnewbies.org
> > https://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies
> 
> 
> -- 
> So many immigrant groups have swept through our town
> that Brooklyn, like Atlantis, reaches mythological
> proportions in the mind of the world - RI Safir 1998
> http://www.mrbrklyn.com 
> 
> DRM is THEFT - We are the STAKEHOLDERS - RI Safir 2002
> http://www.nylxs.com - Leadership Development in Free Software
> http://www2.mrbrklyn.com/resources - Unpublished Archive 
> http://www.coinhangout.com - coins!
> http://www.brooklyn-living.com 
> 
> Being so tracked is for FARM ANIMALS and extermination camps, 
> but incompatible with living as a free human being. -RI Safir 2013
> 

___
Kernelnewbies mailing list
Kernelnewbies@kernelnewbies.org
https://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies

Re: ALSA kernel projects - for academic purposes

[Geraldo Nascimento]

On Fri, Sep 24, 2021 at 10:28:01PM +0530, Muni Sekhar wrote:
> On Fri, Sep 24, 2021 at 10:02 PM Valdis Klētnieks
>  wrote:
> >
> > On Fri, 24 Sep 2021 19:34:59 +0530, Muni Sekhar said:
> > > What small projects would you suggest to a novice with the ALSA
> > > kernel. The aim is to develop a familiarity with the ALSA kernel
> > > source code, and also to submit it for academic purposes.
> >
> > A good place to start is getting a good handle on what the phrase "the ALSA
> > kernel" even means.
> Basically looking for kernel space audio subsystem projects rather
> than its user-space library(alsa-lib) and utilities(alsa-utils).
> >

Hi Muni Sekhar,

I'm not an academicist by far but if you want your patches to be academic,
I think it's more of a question of scientific rigour and scientific
method, such that when the patch(set) is finally accepted by the Linux
community and Linus Torvalds ultimately, you can write a paper about
it.

Obviously there are a lot of things an academicist could bring from his
background to improve the Linux kernel, from the standpoint of security,
code correctness, speed (efficacy), etc.

My suggestion is to ask Takashi Iwai if he has in mind any fun project a
novice academicist could try to do with ALSA. He's the maintainer of
ALSA kernel-side and has a background in academia. He could very well be
the person most able to give the advice you ask for.

Thanks,
Geraldo Nascimento


> > There's the Linux kernel, a small corner of which is the ALSA subsystem for
> > sound.
> >
> 
> 
> -- 
> Thanks,
> Sekhar

___
Kernelnewbies mailing list
Kernelnewbies@kernelnewbies.org
https://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies

[konsole] [Bug 441206] Dolphin crashes after closing it while terminal is open.

[Geraldo Simião]

https://bugs.kde.org/show_bug.cgi?id=441206

--- Comment #26 from Geraldo Simião  ---
yes, it seems the problem at F34 is that the new build dont arrived yet:
dolphin-21.08.0-2.fc34.x86_64
dolphin-libs-21.08.0-2.fc34.x86_64
dolphin-plugins-21.08.0-1.fc34.x86_64

-- 
You are receiving this mail because:
You are watching all bug changes.

[konsole] [Bug 441206] Dolphin crashes after closing it while terminal is open.

[Geraldo Simião]

https://bugs.kde.org/show_bug.cgi?id=441206

--- Comment #25 from Geraldo Simião  ---
tested on the new Fedora 35 pre-release and it works fine there, no bugs

Operating System: Fedora Linux 35
KDE Plasma Version: 5.22.5
KDE Frameworks Version: 5.85.0
Qt Version: 5.15.2
Kernel Version: 5.14.6-300.fc35.x86_64 (64-bit)
Graphics Platform: X11

dolphin-libs-21.08.0-2.fc35.x86_64
dolphin-plugins-21.08.0-1.fc35.x86_64
dolphin-21.08.0-2.fc35.x86_64

-- 
You are receiving this mail because:
You are watching all bug changes.

[konsole] [Bug 441206] Dolphin crashes after closing it while terminal is open.

[Geraldo Simião]

https://bugs.kde.org/show_bug.cgi?id=441206

Geraldo Simião  changed:

   What|Removed |Added

 CC||geraldo.simiao.kutz@gmail.c
   ||om

--- Comment #24 from Geraldo Simião  ---
Created attachment 141750
  --> https://bugs.kde.org/attachment.cgi?id=141750=edit
drkonki kcrash report

report of the same bug happening on Fedora 34 kde spin
Qt Version: 5.15.2
Frameworks Version: 5.85.0
Operating System: Linux 5.13.19-200.fc34.x86_64 x86_64
Windowing System: X11
Drkonqi Version: 5.22.5
Distribution: Fedora 34 (KDE Plasma)

-- 
You are receiving this mail because:
You are watching all bug changes.

Re: [dspace-tech] Dspace 6.3 blank page

[José Geraldo]

er.convert(SqlExceptionHelper.java:109)
>> at
>> org.hibernate.engine.jdbc.internal.LogicalConnectionImpl.obtainConnection(LogicalConnectionImpl.java:221)
>> at
>> org.hibernate.engine.jdbc.internal.LogicalConnectionImpl.getConnection(LogicalConnectionImpl.java:157)
>> at
>> org.hibernate.engine.transaction.internal.jdbc.JdbcTransaction.doBegin(JdbcTransaction.java:67)
>> at
>> org.hibernate.engine.transaction.spi.AbstractTransactionImpl.begin(AbstractTransactionImpl.java:160)
>> at
>> org.hibernate.internal.SessionImpl.beginTransaction(SessionImpl.java:1387)
>> at sun.reflect.GeneratedMethodAccessor153.invoke(Unknown Source)
>> at
>> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>> at java.lang.reflect.Method.invoke(Method.java:498)
>> at
>> org.hibernate.context.internal.ThreadLocalSessionContext$TransactionProtectionWrapper.invoke(ThreadLocalSessionContext.java:352)
>> at com.sun.proxy.$Proxy41.beginTransaction(Unknown Source)
>> at
>> org.dspace.core.HibernateDBConnection.getSession(HibernateDBConnection.java:43)
>> at
>> org.dspace.core.HibernateDBConnection.configureDatabaseMode(HibernateDBConnection.java:154)
>> at
>> org.dspace.core.HibernateDBConnection.setConnectionMode(HibernateDBConnection.java:140)
>> at org.dspace.core.Context.setMode(Context.java:701)
>> at org.dspace.core.Context.init(Context.java:183)
>> at org.dspace.core.Context.(Context.java:126)
>> at
>> org.dspace.app.xmlui.utils.ContextUtil.obtainContext(ContextUtil.java:95)
>> at
>> org.dspace.app.xmlui.utils.ContextUtil.obtainContext(ContextUtil.java:59)
>> at
>> org.dspace.app.xmlui.cocoon.DSpaceLocaleAction.act(DSpaceLocaleAction.java:109)
>> at
>> org.apache.cocoon.sitemap.impl.DefaultExecutor.invokeAction(DefaultExecutor.java:55)
>> at
>> org.apache.cocoon.components.treeprocessor.sitemap.ActTypeNode.invoke(ActTypeNode.java:105)
>> ... 65 more
>> Caused by: java.sql.SQLException: Cannot get a connection, pool error
>> Timeout waiting for idle object
>> at
>> org.apache.commons.dbcp2.PoolingDataSource.getConnection(PoolingDataSource.java:142)
>> at
>> org.apache.commons.dbcp2.BasicDataSource.getConnection(BasicDataSource.java:1533)
>> at
>> org.hibernate.service.jdbc.connections.internal.DatasourceConnectionProviderImpl.getConnection(DatasourceConnectionProviderImpl.java:141)
>> at
>> org.hibernate.internal.AbstractSessionImpl$NonContextualJdbcConnectionAccess.obtainConnection(AbstractSessionImpl.java:301)
>> at
>> org.hibernate.engine.jdbc.internal.LogicalConnectionImpl.obtainConnection(LogicalConnectionImpl.java:214)
>> ... 85 more
>> Caused by: java.util.NoSuchElementException: Timeout waiting for idle
>> object
>> at
>> org.apache.commons.pool2.impl.GenericObjectPool.borrowObject(GenericObjectPool.java:449)
>> at
>> org.apache.commons.pool2.impl.GenericObjectPool.borrowObject(GenericObjectPool.java:363)
>> at
>> org.apache.commons.dbcp2.PoolingDataSource.getConnection(PoolingDataSource.java:134)
>> ... 89 more
>>
>> What could be causing this issue?
>>
>> Hope you guys can help with this one.
>>
>> Juan.
>>
>> --
>> All messages to this mailing list should adhere to the Code of Conduct:
>> https://www.lyrasis.org/about/Pages/Code-of-Conduct.aspx
>> ---
>> You received this message because you are subscribed to the Google Groups
>> "DSpace Technical Support" group.
>> To unsubscribe from this group and stop receiving emails from it, send an
>> email to dspace-tech+unsubscr...@googlegroups.com.
>> To view this discussion on the web visit
>> https://groups.google.com/d/msgid/dspace-tech/b1ccecdf-7012-49be-897a-4aa2c4ed54bcn%40googlegroups.com
>> <https://groups.google.com/d/msgid/dspace-tech/b1ccecdf-7012-49be-897a-4aa2c4ed54bcn%40googlegroups.com?utm_medium=email_source=footer>
>> .
>>
> --
> All messages to this mailing list should adhere to the Code of Conduct:
> https://www.lyrasis.org/about/Pages/Code-of-Conduct.aspx
> ---
> You received this message because you are subscribed to the Google Groups
> "DSpace Technical Support" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to dspace-tech+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/dspace-tech/CAG9P5m_tu98sZAnWd0aUnQCRh8w8hC65-ZWLpfRPeNbjFCMY%3Dg%40mail.gmail.com
> <https://groups.google.com/d/msgid/dspace-tech/CAG9P5m_tu98sZAnWd0aUnQCRh8w8hC65-ZWLpfRPeNbjFCMY%3Dg%40mail.gmail.com?utm_medium=email_source=footer>
> .
>


-- 
At.te,

José Geraldo

-- 
All messages to this mailing list should adhere to the Code of Conduct: 
https://www.lyrasis.org/about/Pages/Code-of-Conduct.aspx
--- 
You received this message because you are subscribed to the Google Groups 
"DSpace Technical Support" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to dspace-tech+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/dspace-tech/CANP4ikQD7GR-pUcWUCgmJS%3DVO986BQmQRxtBss6%3Drj2bv%3D%3DOpQ%40mail.gmail.com.

Re: [dspace-tech] Problems with dspace

[José Geraldo]

Check your Dspace log or send it to analyse.

Em sex, 17 de set de 2021 14:33, Saulo Hernandez 
escreveu:

> In recent days we had to turn off the server where our dspace is hosted
> and when we turn it on again it does not work, I turn on aoache, turn on
> tomcat but the xmlui and jspui resources are not accessible, who can help
> me please
>
> --
> All messages to this mailing list should adhere to the Code of Conduct:
> https://www.lyrasis.org/about/Pages/Code-of-Conduct.aspx
> ---
> You received this message because you are subscribed to the Google Groups
> "DSpace Technical Support" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to dspace-tech+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/dspace-tech/5ac12f3a-6e74-4560-a04a-9a8708d500d1n%40googlegroups.com
> 
> .
>

-- 
All messages to this mailing list should adhere to the Code of Conduct: 
https://www.lyrasis.org/about/Pages/Code-of-Conduct.aspx
--- 
You received this message because you are subscribed to the Google Groups 
"DSpace Technical Support" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to dspace-tech+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/dspace-tech/CANP4ikRxV-DLrv8BLFoHAYYPB5X500CPYX8u50-6kF4Q_rQvHQ%40mail.gmail.com.

Re: [dspace-tech] Consulta sobre la Ayuda de Dspace

[José Geraldo]

This is help
https://github.com/DSpace/DSpace/blob/dspace-6.3/dspace-jspui/src/main/webapp/help/index.html
?

Need translate/custom your help page.

Em sex., 17 de set. de 2021 às 00:24, Alexis Gamboa 
escreveu:

> Buenas noches, alguien sabe como mostrar la ayuda de Dspace 6.3 en
> español.
>
> Gracias
>
> --
> All messages to this mailing list should adhere to the Code of Conduct:
> https://www.lyrasis.org/about/Pages/Code-of-Conduct.aspx
> ---
> You received this message because you are subscribed to the Google Groups
> "DSpace Technical Support" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to dspace-tech+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/dspace-tech/CAMOFNxfo6g-gMxxQhGZ%2BHJqaCr6asXXOKOTX0wrxM_EwFDC0YA%40mail.gmail.com
> <https://groups.google.com/d/msgid/dspace-tech/CAMOFNxfo6g-gMxxQhGZ%2BHJqaCr6asXXOKOTX0wrxM_EwFDC0YA%40mail.gmail.com?utm_medium=email_source=footer>
> .
>


-- 
At.te,

José Geraldo

-- 
All messages to this mailing list should adhere to the Code of Conduct: 
https://www.lyrasis.org/about/Pages/Code-of-Conduct.aspx
--- 
You received this message because you are subscribed to the Google Groups 
"DSpace Technical Support" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to dspace-tech+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/dspace-tech/CANP4ikS4%2ByeFX11jn%2B%3D3AwsnM2m9ctFbwtJY%3Dtm9iUu-LWz%2BQg%40mail.gmail.com.

Re: Test request for BZ 1996998

[Geraldo Simião Kutz]

Tested the fix. Works fine.

Em ter, 14 de set de 2021 11:19, Ben Cotton  escreveu:

> Hi folks,
>
> Halfline has provided a candidate fix for BZ 1996998. Please get the
> build from Koji[1] and test.
>
> [1] https://koji.fedoraproject.org/koji/taskinfo?taskID=75662323
>
> --
> Ben Cotton
> He / Him / His
> Fedora Program Manager
> Red Hat
> TZ=America/Indiana/Indianapolis
> ___
> test mailing list -- test@lists.fedoraproject.org
> To unsubscribe send an email to test-le...@lists.fedoraproject.org
> Fedora Code of Conduct:
> https://docs.fedoraproject.org/en-US/project/code-of-conduct/
> List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
> List Archives:
> https://lists.fedoraproject.org/archives/list/test@lists.fedoraproject.org
> Do not reply to spam on the list, report it:
> https://pagure.io/fedora-infrastructure
>
___
test mailing list -- test@lists.fedoraproject.org
To unsubscribe send an email to test-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/test@lists.fedoraproject.org
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure

Re: Donate 1 minute of your time to test upgrades from F34 to F35

[Geraldo Simião Kutz]

I tested in a F33 KDE spin too.
All good, no problems.

Instalar   125 Pacotes
Atualizar 1737 Pacotes
Remover  3 Pacotes
Desatualizar 3 Pacotes


Em ter., 7 de set. de 2021 às 13:15, Miroslav Suchý 
escreveu:

> Do you want to make Fedora 35 better? Please spend 1 minute of your time
> and try to run:
>
> # Run this only if you use default Fedora modules
> # next time you run any DNF command default modules will be enabled again
> sudo dnf module reset '*'
>
> sudo dnf --releasever=35 --setopt=module_platform_id=platform:f35 \
>
> --enablerepo=updates-testing --enablerepo=updates-testing-modular \
> distro-sync
>
> This command does not replace `dnf system-upgrade`, but it will reveal
> potential problems.
>
> You may also run `dnf upgrade` before running this command.
>
> If you get this prompt:
>
> ...
> Total download size: XXX M
> Is this ok [y/N]:
>
> you can answer N and nothing happens, no need to test the actual upgrade.
>
> But very likely you get some dependency problem now. In that case, please
> report it against the appropriate package.
>
> Or against fedora-obsolete-packages if that package should be removed in
> Fedora 35. Please check existing reports against
>
> fedora-obsolete-packages first:
>
> https://red.ht/2kuBDPu
>
>
> and also there is already bunch of "Fails to install" (F35FailsToInstall)
> reports:
>
>
> https://bugzilla.redhat.com/buglist.cgi?bug_id=1927313_id_type=anddependson=tvp_id=12125305#
>
> Thank you
> Miroslav
> ___
> devel mailing list -- devel@lists.fedoraproject.org
> To unsubscribe send an email to devel-le...@lists.fedoraproject.org
> Fedora Code of Conduct:
> https://docs.fedoraproject.org/en-US/project/code-of-conduct/
> List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
> List Archives:
> https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
> Do not reply to spam on the list, report it:
> https://pagure.io/fedora-infrastructure
>
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure

Upgrading Hadoop 3.3.1 dependencies

[Geraldo Netto]

Dear Friends,

May I ask your help regarding Hadoop 3.3.1 dependency updates?
I'm trying to upgrade old and/or vulnerable Hadoop dependencies
and by now I have the following maven dependencies set (maven
dependencies below)

By any chance do you have any suggestions on how to handle
dependencies in a better way?
Also, I just need the HDFS support, not all Hadoop, but because I
don`t know what might be required
everything is included



3.3.1
9.4.43.v20210629
4.1.66.Final
1.19.4





junit
junit
test


org.jmockit
jmockit
test


io.netty
netty-all
${netty.version}



com.google.guava
guava
30.1.1-jre


org.apache.commons
commons-csv
1.8


org.apache.commons
commons-text
${commons-text.version}


org.eclipse.jetty
jetty-server
${jetty.version}


org.eclipse.jetty
jetty-util
${jetty.version}


org.eclipse.jetty
jetty-servlet
${jetty.version}


org.eclipse.jetty
jetty-webapp
${jetty.version}


org.eclipse.jetty
jetty-util-ajax
${jetty.version}


com.sun.jersey
jersey-client
${jersey.version}


com.sun.jersey
jersey-core
${jersey.version}


com.sun.jersey
jersey-servlet
${jersey.version}


com.sun.jersey
jersey-json
${jersey.version}


com.sun.jersey
jersey-server
${jersey.version}



org.apache.hadoop
hadoop-common
${hadoop.version}


log4j
log4j


org.slf4j
slf4j-log4j12


io.netty
netty-transport-native-epoll


io.netty
netty-common


io.netty
netty-common


io.netty
netty-buffer


io.netty
netty-transport


io.netty
netty-resolver


io.netty
netty-transport-native-unix-common


io.netty
netty-handler


io.netty
netty-codec




org.apache.hadoop
hadoop-hdfs
${hadoop.version}


log4j
log4j


io.netty
netty




org.apache.hadoop
hadoop-client
${hadoop.version}


log4j
log4j


org.slf4j
slf4j-log4j12


org.apache.hadoop
hadoop-aws


org.apache.hadoop
hadoop-yarn-common


org.apache.hadoop
hadoop-yarn-api


org.apache.hadoop
hadoop-yarn-client


org.apache.hadoop
hadoop-mapreduce-client-core


org.apache.hadoop
hadoop-mapreduce-client-jobclient




org.apache.hadoop
hadoop-minicluster
${hadoop.version}
test




Thank you very much/Kind Regards,

Geraldo Netto
site: http://exdev.sf.net
github: https://github.com/geraldo-netto
linkedin: https://www.linkedin.com/in/geraldonetto
facebook: https://web.facebook.com/geraldo.netto.161

Re: how to improve qcow performance?

[Geraldo Netto]

Dear Nir/Friends,

On Tue, 20 Jul 2021 at 11:34, Nir Soffer  wrote:
>
> On Thu, Jul 15, 2021 at 2:33 PM Geraldo Netto  wrote:
> >
> > Dear Friends,
> >
> > I beg your pardon for such a newbie question
> > But I would like to better understand how to improve the qcow performance
>
> I guess you mean how to improve "qcow2" performance. If you use "qcow"
> format the best way is to switch to "qcow2".

I read here [1] there was a qcow3, but it seems that page is
deprecated (last update on sept. 2016)

> > I was checking the qemu-img and it seems that the following parameters
> > are the most relevant to optimise the performance, no?
> >
> >   'cache' is the cache mode used to write the output disk image, the valid
> > options are: 'none', 'writeback' (default, except for convert),
> > 'writethrough',
> > 'directsync' and 'unsafe' (default for convert)
> >
> > Should I infer that directsync means bypass all the stack and write
> > directly to the disk?
>
> 'directsync' is using direct I/O, but calls fsync() for every write. This is
> the slowest way and does not make sense for converting images.
>
> 'none' uses direct I/O (O_DIRECT). This enables native async I/O (libaio)
> which can give better performance in some cases.
>
> 'writeback' uses the page cache, considering the write complete when the
> data is in the page cache, and reading data from the page cache. This is
> likely to give the best performance, but is also likely to give inconsistent
> performance and cause trouble for other applications.
>
> The kernel will write a huge amount of data to the page cache, and from time
> to time try to flush a huge amount of data, which can cause long delays in
> other processes accessing the same storage. It also pollutes the page cache
> with data that may not be needed after the image is converted, for example
> when you convert an image on one host, writing to shared storage, and the
> image is used later on another host.
>
> 'writethrough' seems to use the pagecache, but it reports writes only after
> data is flushed so it will be slow as 'directsync' for writing, and
> can cause the
> same issues with the page cache as 'writeback'.
>
> 'unsafe' (default for convert) means writes are never flushed to disk, which 
> is
> unsafe when using in vm's -drive option, but completely safe when using in
> qemu-img convert, since qemu-img completes the operation with fsync().
>
> The most important option for performance is -W (unordered writes).
> For writing to block devices, it is up to 6 times faster. But it can cause
> fragmentation so you may get faster copies but accessing the image
> later may be slower.

I see! Now I get it

> Check this for example of -W usage:
> https://bugzilla.redhat.com/1511891#c57
>
> Finally there is the -m option - the default value (8) gives good performance,
> but using -m 16 can be a little faster.
>
> >   'src_cache' is the cache mode used to read input disk images, the valid
> > options are the same as for the 'cache' option
> >
> > I didn`t follow where should I look to check the 'cache' options :`(
>
>-t CACHE
>   Specifies  the cache mode that should be used with the
> (destination) file.
>   See the documentation of the emulator's -drive cache=...
> option for allowed values.
>
> "See the documentation of the amulator -drive cache=" means see qemu(1).
>
> > I guess that using smaller files is more performance due to the
> > reduced number of metadata to handle?
>
> What do you mean by smaller files?

I mean, by reducing the size of a qcow image and distribute them among
different NAS
it would reduce the pressure on metadata updating of the qcow image
and that would reflect in better performance, no? (it`s just an intuition)

Just to describe the scenario, we have an all cloud env. using
kubernetes with longhorn
and behind the scenes there are qcow images mapped for each block
device exposed on kubernetes
We are studying ways to optimise it and specially replace the NFS
architecture that we have now (too slow for our needs)

> > In any case, I saw the qemu-io command and I plan to stress test it
>
> The best test is to measure the actual operation with qemu-img convert
> with different options and the relevant storage.

Interesting catch, will certainly check it out!!!

> Nir
>


[1] https://wiki.qemu.org/Features/Qcow3


Geraldo Netto
site: http://exdev.sf.net
github: https://github.com/geraldo-netto
linkedin: https://www.linkedin.com/in/geraldonetto
facebook: https://web.facebook.com/geraldo.netto.161

how to improve qcow performance?

[Geraldo Netto]

Dear Friends,

I beg your pardon for such a newbie question
But I would like to better understand how to improve the qcow performance

I was checking the qemu-img and it seems that the following parameters
are the most relevant to optimise the performance, no?

  'cache' is the cache mode used to write the output disk image, the valid
options are: 'none', 'writeback' (default, except for convert),
'writethrough',
'directsync' and 'unsafe' (default for convert)

Should I infer that directsync means bypass all the stack and write
directly to the disk?

  'src_cache' is the cache mode used to read input disk images, the valid
options are the same as for the 'cache' option

I didn`t follow where should I look to check the 'cache' options :`(

I guess that using smaller files is more performance due to the
reduced number of metadata to handle?
In any case, I saw the qemu-io command and I plan to stress test it


Thank you very much/Kind Regards,

Geraldo Netto
site: http://exdev.sf.net
github: https://github.com/geraldo-netto
linkedin: https://www.linkedin.com/in/geraldonetto
facebook: https://web.facebook.com/geraldo.netto.161

Re: PipeWire issues with <= 0.3.24

[Geraldo Simião Kutz]

Hi, great to hear that problem is solved.

Maybe it's just a FinalFE not necessary a blocker.

Regards
Geraldo
geraldosimao

Em seg, 19 de abr de 2021 11:23, Garrett LeSage 
escreveu:

> Hi all,
>
> Several weeks ago, while running Fedora 34 pre-beta, I had a bunch of
> PipeWire issues preventing me from successfully doing video conferences and
> listening to music. I reported the issues upstream. The problems included
> using Bluetooth headphones (at all), codecs for the headphones, switching
> outputs, and issues when doing video calls. It was a mess, multiple times a
> day.
>
> I'm happy to say they were all fixed with the latest release of
> pipewire-0.3.25-1.fc34 and my system has been mostly problem-free with
> audio since upgrading.
>
> However, after two weeks, this bugfix version is still in testing... and
> doesn't like it will make it for Fedora 34 at this moment:
> https://bodhi.fedoraproject.org/updates/FEDORA-2021-46a2394c6d
>
> I hope all these fixes will make it in time for the release. It'd be awful
> if people would associate PipeWire (and Fedora 34) with broken audio (like
> so many did for PulseAudio), as it's awesome and actually works very well
> as of 0.3.25.
>
> Could we make this a blocker, so that this newer version (0.3.15) will be
> included in the release?
>
> Thanks,
> Garrett
> ___
> test mailing list -- test@lists.fedoraproject.org
> To unsubscribe send an email to test-le...@lists.fedoraproject.org
> Fedora Code of Conduct:
> https://docs.fedoraproject.org/en-US/project/code-of-conduct/
> List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
> List Archives:
> https://lists.fedoraproject.org/archives/list/test@lists.fedoraproject.org
> Do not reply to spam on the list, report it:
> https://pagure.io/fedora-infrastructure
>
___
test mailing list -- test@lists.fedoraproject.org
To unsubscribe send an email to test-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/test@lists.fedoraproject.org
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure

Re: [dspace-tech] Re: Direct DB access for critical data?

[José Geraldo]

This is can help you:

https://wiki.lyrasis.org/display/DSDOC6x/Storage+Layer?preview=/68069687/78157937/dspace6.png

Em ter., 6 de abr. de 2021 às 13:40, Chris Clawson 
escreveu:

> Well, I have discovered a very helpful discussion here:
> https://wiki.lyrasis.org/display/DSPACE/The+metadatavalue+table
> It only cites some very limited examples. Does anyone have links or access
> to a discussion with examples which could return my description field?
>
> On Tuesday, April 6, 2021 at 10:26:40 AM UTC-4 Chris Clawson wrote:
>
>> I have a DSpace 6.3 installation I am trying to pair with a Wordpress
>> website, on the same public server. I am attempting to access DSpace
>> content to populate pages in Wordpress and have made some crude successes.
>>
>> What I would like to do is to write AJAX applications using server side
>> queries (for Wordpress pages), written in PHP, to directly access the
>> DSpace database in Postgresql.
>>
>> The DSpace database tables are a mystery to me. I can list them, but
>> can't find my most critical data: Item titles, descriptions and handles.
>>
>> Could you please comment and hopefully point me to the correct DB tables
>> or how I might directly get this information from the Postgre server?
>>
> --
> All messages to this mailing list should adhere to the Code of Conduct:
> https://duraspace.org/about/policies/code-of-conduct/
> ---
> You received this message because you are subscribed to the Google Groups
> "DSpace Technical Support" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to dspace-tech+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/dspace-tech/453554a3-46d5-4c1a-b39b-331ed98feaccn%40googlegroups.com
> <https://groups.google.com/d/msgid/dspace-tech/453554a3-46d5-4c1a-b39b-331ed98feaccn%40googlegroups.com?utm_medium=email_source=footer>
> .
>


-- 
At.te,

José Geraldo

-- 
All messages to this mailing list should adhere to the Code of Conduct: 
https://duraspace.org/about/policies/code-of-conduct/
--- 
You received this message because you are subscribed to the Google Groups 
"DSpace Technical Support" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to dspace-tech+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/dspace-tech/CANP4ikRANh7n4c%3Dhiv0q3N9AV%3DcmSR5yzewC0ZDpuok8%2BUr-gQ%40mail.gmail.com.

Re: libplacebo conflicts in f34 repo

[Geraldo Simião Kutz]

Hello Misterx42

You will see there is a new update now on RPM fusion from "mpv
0.33.0-6.fc34" and this new build solves the dependency problem.

best regards

Geraldo

geraldosimiao




Em sex., 2 de abr. de 2021 às 15:18, misterx42--- via test <
test@lists.fedoraproject.org> escreveu:

> I'm not sure if this is supposed to go to the bug tracker, so I thought
> I'll report it here first.
>
> libplacebo is currently being blocked from upgrading due to mpv's
> dependency on the old version:
>
> Problem: package mpv-0.33.0-5.fc34.x86_64 requires
> libplacebo.so.104()(64bit), but none of the providers can be installed
>   - cannot install both libplacebo-3.120.0-1.fc34.x86_64 and
> libplacebo-3.104.0-1.fc34.x86_64
>   - cannot install both libplacebo-3.104.0-1.fc34.x86_64 and
> libplacebo-3.120.0-1.fc34.x86_64
>   - cannot install the best update candidate for package
> mpv-0.33.0-5.fc34.x86_64
>   - cannot install the best update candidate for package
> libplacebo-3.104.0-1.fc34.x86_64
>
> This is my first time running a Beta version for Fedora, so I don't know
> if these problems are expected and will be resolved automatically, thus I
> haven't opened a bug yet - figured it's better to ask than to add more work
> to people.
> ___
> test mailing list -- test@lists.fedoraproject.org
> To unsubscribe send an email to test-le...@lists.fedoraproject.org
> Fedora Code of Conduct:
> https://docs.fedoraproject.org/en-US/project/code-of-conduct/
> List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
> List Archives:
> https://lists.fedoraproject.org/archives/list/test@lists.fedoraproject.org
> Do not reply to spam on the list, report it:
> https://pagure.io/fedora-infrastructure
>
___
test mailing list -- test@lists.fedoraproject.org
To unsubscribe send an email to test-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/test@lists.fedoraproject.org
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure

Re: [dspace-tech] Getting Backups

[José Geraldo]

This can help you: https://wiki.lyrasis.org/display/DSPACE/BackupRestore

Em seg., 29 de mar. de 2021 às 11:29, Ramani Sunethra Liyanarachchi <
ramsunet...@gmail.com> escreveu:

> Kindly let me instruct steps to get backups of Dspace.
>
> --
>
> *R. Sunethra Liyanarachchi*
>
> *Librarian*
>
> *NARA Library*
>
> *Crow Island*
>
> *Colombo 15*
> *Sri Lanka*
>
>
>
> *Tel: 94+11+2521633*
>
>
>
> *http://ramani-fisheriesaquaticresources.blogspot.com
> <http://ramani-fisheriesaquaticresources.blogspot.com>*
>
> --
> All messages to this mailing list should adhere to the Code of Conduct:
> https://duraspace.org/about/policies/code-of-conduct/
> ---
> You received this message because you are subscribed to the Google Groups
> "DSpace Technical Support" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to dspace-tech+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/dspace-tech/CAGEO7wG9KAReVKp%2Bg5sT3Nb4S8bcZTzuy_EZRhJ%3DcSV2ctxsBw%40mail.gmail.com
> <https://groups.google.com/d/msgid/dspace-tech/CAGEO7wG9KAReVKp%2Bg5sT3Nb4S8bcZTzuy_EZRhJ%3DcSV2ctxsBw%40mail.gmail.com?utm_medium=email_source=footer>
> .
>


-- 
At.te,

José Geraldo

-- 
All messages to this mailing list should adhere to the Code of Conduct: 
https://duraspace.org/about/policies/code-of-conduct/
--- 
You received this message because you are subscribed to the Google Groups 
"DSpace Technical Support" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to dspace-tech+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/dspace-tech/CANP4ikQG72XQKFZp8z6pPsLPb%3DunUsBjEwb2Th7ps4G6rj%3DkWA%40mail.gmail.com.

Re: [dspace-tech] PostgreSQL Backup and Restore methods

[José Geraldo]

Were you able to view after copying?

Em sex., 26 de mar. de 2021 às 12:59, Maya Zbitneva 
escreveu:

> Thank you for the answer.
> What do you mean under word "import"?
> I just copied assetstore before pg_dump and copied it back after
> pg_restore. Is it right?
>
>
> пятница, 26 марта 2021 г. в 16:03:54 UTC+2, jos...@gmail.com:
>
>> Don't see the files?
>>
>> Did you import the assetstore directory?
>>
>>- [dspace]/assetstore
>>
>>
>> Em sex., 26 de mar. de 2021 às 10:03, Maya Zbitneva 
>> escreveu:
>>
>>> Good day!
>>>
>>> Could you help me please to solve the problem:
>>>
>>> I tried to make Backup and Restore procedure
>>>
>>>
>>> https://wiki.lyrasis.org/display/DSDOC6x/Storage+Layer#StorageLayer-MaintenanceandBackup
>>>
>>> using PostgreSQL Backup and Restore
>>> <http://www.postgresql.org/docs/current/static/backup.html> methods.
>>>
>>> I used two scenarios:
>>>
>>> First one:
>>>
>>> 1) pg_dump dspace > dspace.sql
>>>
>>> 2) stop tomcat
>>>
>>> 3) dropdb dspace
>>>
>>> 4) createdb --username=postgres --owner=dspace --encoding=UNICODE dspace
>>>
>>> 5) psql -d dspace -f dspace.sql
>>>
>>> 6) start tomcat
>>>
>>> Second one:
>>>
>>> 1) pg_dump dspace -F c -f dspace.dat
>>>
>>> 2) stop tomcat
>>>
>>> 3) dropdb dspace
>>>
>>> 4)createdb --username=postgres --owner=dspace --encoding=UNICODE dspace
>>>
>>> 5) *pg_restore -d **dspace** d**space**.d**at*
>>>
>>>
>>> *6) start tomcat.*
>>>
>>> *And I obtained **the following result: I restored communities,
>>> collections. And I did not restore items in all collections in both
>>> scenarios.*
>>>
>>> *Question: What i did **wrong**? *
>>>
>>>
>>> --
>>> All messages to this mailing list should adhere to the Code of Conduct:
>>> https://duraspace.org/about/policies/code-of-conduct/
>>> ---
>>> You received this message because you are subscribed to the Google
>>> Groups "DSpace Technical Support" group.
>>> To unsubscribe from this group and stop receiving emails from it, send
>>> an email to dspace-tech...@googlegroups.com.
>>> To view this discussion on the web visit
>>> https://groups.google.com/d/msgid/dspace-tech/a098cd6e-2d12-4e49-8084-07ed5b2cb6ffn%40googlegroups.com
>>> <https://groups.google.com/d/msgid/dspace-tech/a098cd6e-2d12-4e49-8084-07ed5b2cb6ffn%40googlegroups.com?utm_medium=email_source=footer>
>>> .
>>>
>>
>>
>> --
>> At.te,
>>
>> José Geraldo
>>
>> --
> All messages to this mailing list should adhere to the Code of Conduct:
> https://duraspace.org/about/policies/code-of-conduct/
> ---
> You received this message because you are subscribed to the Google Groups
> "DSpace Technical Support" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to dspace-tech+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/dspace-tech/1413de05-884c-4568-89ba-469e0b6261ean%40googlegroups.com
> <https://groups.google.com/d/msgid/dspace-tech/1413de05-884c-4568-89ba-469e0b6261ean%40googlegroups.com?utm_medium=email_source=footer>
> .
>


-- 
At.te,

José Geraldo

-- 
All messages to this mailing list should adhere to the Code of Conduct: 
https://duraspace.org/about/policies/code-of-conduct/
--- 
You received this message because you are subscribed to the Google Groups 
"DSpace Technical Support" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to dspace-tech+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/dspace-tech/CANP4ikQeBxGio3bqxuNmtKSh0qOMEq5yjdnA3YkubpQUKq7vLg%40mail.gmail.com.

Re: [dspace-tech] PostgreSQL Backup and Restore methods

[José Geraldo]

Don't see the files?

Did you import the assetstore directory?

   - [dspace]/assetstore


Em sex., 26 de mar. de 2021 às 10:03, Maya Zbitneva 
escreveu:

> Good day!
>
> Could you help me please to solve the problem:
>
> I tried to make Backup and Restore procedure
>
>
> https://wiki.lyrasis.org/display/DSDOC6x/Storage+Layer#StorageLayer-MaintenanceandBackup
>
> using PostgreSQL Backup and Restore
> <http://www.postgresql.org/docs/current/static/backup.html> methods.
>
> I used two scenarios:
>
> First one:
>
> 1) pg_dump dspace > dspace.sql
>
> 2) stop tomcat
>
> 3) dropdb dspace
>
> 4) createdb --username=postgres --owner=dspace --encoding=UNICODE dspace
>
> 5) psql -d dspace -f dspace.sql
>
> 6) start tomcat
>
> Second one:
>
> 1) pg_dump dspace -F c -f dspace.dat
>
> 2) stop tomcat
>
> 3) dropdb dspace
>
> 4)createdb --username=postgres --owner=dspace --encoding=UNICODE dspace
>
> 5) *pg_restore -d **dspace** d**space**.d**at*
>
>
> *6) start tomcat.*
>
> *And I obtained **the following result: I restored communities,
> collections. And I did not restore items in all collections in both
> scenarios.*
>
> *Question: What i did **wrong**? *
>
>
> --
> All messages to this mailing list should adhere to the Code of Conduct:
> https://duraspace.org/about/policies/code-of-conduct/
> ---
> You received this message because you are subscribed to the Google Groups
> "DSpace Technical Support" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to dspace-tech+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/dspace-tech/a098cd6e-2d12-4e49-8084-07ed5b2cb6ffn%40googlegroups.com
> <https://groups.google.com/d/msgid/dspace-tech/a098cd6e-2d12-4e49-8084-07ed5b2cb6ffn%40googlegroups.com?utm_medium=email_source=footer>
> .
>


-- 
At.te,

José Geraldo

-- 
All messages to this mailing list should adhere to the Code of Conduct: 
https://duraspace.org/about/policies/code-of-conduct/
--- 
You received this message because you are subscribed to the Google Groups 
"DSpace Technical Support" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to dspace-tech+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/dspace-tech/CANP4ikR8nm8ziU_vCiYCjDirR%3DKhEKbuekd7Z4OdnfrCMPw8ww%40mail.gmail.com.

Re: [dspace-tech] Error when uploading a PDF item

[José Geraldo]

Simulate the error in next send your dspace log file to detail the error.
Error Log Files

   - *DSpace log:* [dspace]/log/dspace.log (*usually*)
  - [dspace] is the location where DSpace is installed.


Em qui., 18 de mar. de 2021 às 16:36, Saul Hernandez O. 
escreveu:

>
> Error when uploading a PDF item, this only happens with some pdf's, I
> could not find the error, hopefully you could help me, the interface is
> custom xmlui-mirage2
>
>
> I attach a document with the screens
>
> --
> All messages to this mailing list should adhere to the Code of Conduct:
> https://duraspace.org/about/policies/code-of-conduct/
> ---
> You received this message because you are subscribed to the Google Groups
> "DSpace Technical Support" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to dspace-tech+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/dspace-tech/6beaeb9d-ce5a-4a4b-96c7-d5334807bcbdn%40googlegroups.com
> <https://groups.google.com/d/msgid/dspace-tech/6beaeb9d-ce5a-4a4b-96c7-d5334807bcbdn%40googlegroups.com?utm_medium=email_source=footer>
> .
>


-- 
At.te,

José Geraldo

-- 
All messages to this mailing list should adhere to the Code of Conduct: 
https://duraspace.org/about/policies/code-of-conduct/
--- 
You received this message because you are subscribed to the Google Groups 
"DSpace Technical Support" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to dspace-tech+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/dspace-tech/CANP4ikTkmsHpBrqjX%3DZm2LfQk4J1rVLqiD-4%2BFj9AvcUWzea9Q%40mail.gmail.com.

Re: [dspace-tech] Dspace maximum file size

[José Geraldo]

Hi,

https://github.com/DSpace/DSpace/blob/dspace-6.3/dspace/config/dspace.cfg#L1571

Em ter, 16 de mar de 2021 22:10, Saul Hernandez O.  escreveu:

> Hello everyone!
> I am investigating what is the maximum file size
> that dspace accepts  in xmlui
>
> Thank you!
>
> --
> All messages to this mailing list should adhere to the Code of Conduct:
> https://duraspace.org/about/policies/code-of-conduct/
> ---
> You received this message because you are subscribed to the Google Groups
> "DSpace Technical Support" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to dspace-tech+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/dspace-tech/3e591cd5-338d-461e-ad06-4aeb97476b1fn%40googlegroups.com
> 
> .
>

-- 
All messages to this mailing list should adhere to the Code of Conduct: 
https://duraspace.org/about/policies/code-of-conduct/
--- 
You received this message because you are subscribed to the Google Groups 
"DSpace Technical Support" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to dspace-tech+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/dspace-tech/CANP4ikRP2dkPZuetgcBAWYvv3kTOjxvU%2BEs53saO%2BUCgvVe9Yw%40mail.gmail.com.

Re: [dspace-tech] Package located at site aip does not exist

[José Geraldo]

There are other ways to backup and restore (migrate) an instance of Dspace:

https://wiki.lyrasis.org/display/DSPACE/BackupRestore

If your path is not working, then I suggested another way to backup and
restore, as described in the previous link.

Em ter., 16 de mar. de 2021 às 10:11, Κωνσταντίνος Πετρίδης <
kpetridi...@gmail.com> escreveu:

> Sorry, but I am not quite sure what you are proposing here. This is not an
> upgrade attempt, I am just trying to restore the data I had, I wouldn't
> even call it a migration, it's just a "restore and backup" using AIP.
>
> Στις Τρί, 16 Μαρ 2021 στις 2:16 μ.μ., ο/η José Geraldo 
> έγραψε:
>
>> As commented before, was a migration suggestion alternate.
>>
>> Em ter., 16 de mar. de 2021 às 04:15, kpet 
>> escreveu:
>>
>>> Hello,
>>>
>>> I am not sure what you are refering to. Why would I need to copy the
>>> database manually? Isn't that what the packager does for me?
>>> The only thing I have manually copied is a custom schema and some custom
>>> elements in the local schema. Should I copy other settings as well before
>>> the transport is possible?
>>>
>>>
>>> Στις Δευτέρα, 15 Μαρτίου 2021 στις 3:13:27 μ.μ. UTC+2, ο χρήστης
>>> jos...@gmail.com έγραψε:
>>>
>>>> Hi,
>>>>
>>>> Are you tried making a copy from database and from assetstore directory
>>>> in new instance?
>>>>
>>>> Is this a migration option.
>>>>
>>>> Em sáb., 13 de mar. de 2021 às 14:35, kpet 
>>>> escreveu:
>>>>
>>>>>
>>>>> Hello,
>>>>>
>>>>> I am using DSpace 6.3, and I am trying to move my DSpace installation
>>>>> from one pc to another.
>>>>>
>>>>> I have successfully exported the whole hierarchy via the following
>>>>> command, as stated in the docs (values were changed):
>>>>> *[dspace]/bin/dspace packager -d -a -t AIP -e ad...@myu.edu -i 4321/0
>>>>> sitewide-aip.zip*
>>>>>
>>>>> I have also successfully installed DSpace on the new location and have
>>>>> verified it is working. Now I need to restore the whole hierarchy using
>>>>> that sitewide-aip.zip
>>>>>
>>>>> I tried running the packager with all options available  [-s, -r
>>>>> (-k/-f)] but none work. The cmd just prints "ERROR: Package located at
>>>>> sitewide-aip.zip does not exist".
>>>>>
>>>>> Any help would be appreciated!
>>>>>
>>>>> --
>>>>> All messages to this mailing list should adhere to the Code of
>>>>> Conduct: https://duraspace.org/about/policies/code-of-conduct/
>>>>> ---
>>>>> You received this message because you are subscribed to the Google
>>>>> Groups "DSpace Technical Support" group.
>>>>> To unsubscribe from this group and stop receiving emails from it, send
>>>>> an email to dspace-tech...@googlegroups.com.
>>>>> To view this discussion on the web visit
>>>>> https://groups.google.com/d/msgid/dspace-tech/fe1b8862-aab6-49d4-b044-f931494042d7n%40googlegroups.com
>>>>> <https://groups.google.com/d/msgid/dspace-tech/fe1b8862-aab6-49d4-b044-f931494042d7n%40googlegroups.com?utm_medium=email_source=footer>
>>>>> .
>>>>>
>>>>
>>>>
>>>> --
>>>> At.te,
>>>>
>>>> José Geraldo
>>>>
>>>> --
>>> All messages to this mailing list should adhere to the Code of Conduct:
>>> https://duraspace.org/about/policies/code-of-conduct/
>>> ---
>>> You received this message because you are subscribed to the Google
>>> Groups "DSpace Technical Support" group.
>>> To unsubscribe from this group and stop receiving emails from it, send
>>> an email to dspace-tech+unsubscr...@googlegroups.com.
>>> To view this discussion on the web visit
>>> https://groups.google.com/d/msgid/dspace-tech/5aa1ea6c-40ce-418e-9e05-d396445e08dcn%40googlegroups.com
>>> <https://groups.google.com/d/msgid/dspace-tech/5aa1ea6c-40ce-418e-9e05-d396445e08dcn%40googlegroups.com?utm_medium=email_source=footer>
>>> .
>>>
>>
>>
>> --
>> At.te,
>>
>> José Geraldo
>>
>>
>
> --
>
> Costas Petridis
>
> Terracom S.A.
> Phone: +30-26510-94333
> Email: kpetri...@terracom.gr
> Skype: live:.cid.6549953089921dc8
> Website: www.terracom.gr
> Address: Ethnikis Antistasis 79, Katsikas | Ioannina 45221 | Greece
> [image: Facebook] <https://www.facebook.com/terracom/> [image: Twitter]
> <https://twitter.com/Terracom_GR> [image: Linkedin]
> <https://www.linkedin.com/company/terracom-sa/>
> VISIT US AT CES 2020 - JAN 7-10, 2020 - LAS VEGAS, NV
> [image: ces2020]
> <https://www.spotypal.com/blog/spotypal-participating-ces-2020/>
>


-- 
At.te,

José Geraldo

-- 
All messages to this mailing list should adhere to the Code of Conduct: 
https://duraspace.org/about/policies/code-of-conduct/
--- 
You received this message because you are subscribed to the Google Groups 
"DSpace Technical Support" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to dspace-tech+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/dspace-tech/CANP4ikRzH1SvqBMFOg4p2UuSM4HxFqk0%3DRnN2F_D8Y%3DnDYBgkQ%40mail.gmail.com.

Re: [dspace-tech] Package located at site aip does not exist

[José Geraldo]

As commented before, was a migration suggestion alternate.

Em ter., 16 de mar. de 2021 às 04:15, kpet  escreveu:

> Hello,
>
> I am not sure what you are refering to. Why would I need to copy the
> database manually? Isn't that what the packager does for me?
> The only thing I have manually copied is a custom schema and some custom
> elements in the local schema. Should I copy other settings as well before
> the transport is possible?
>
>
> Στις Δευτέρα, 15 Μαρτίου 2021 στις 3:13:27 μ.μ. UTC+2, ο χρήστης
> jos...@gmail.com έγραψε:
>
>> Hi,
>>
>> Are you tried making a copy from database and from assetstore directory
>> in new instance?
>>
>> Is this a migration option.
>>
>> Em sáb., 13 de mar. de 2021 às 14:35, kpet  escreveu:
>>
>>>
>>> Hello,
>>>
>>> I am using DSpace 6.3, and I am trying to move my DSpace installation
>>> from one pc to another.
>>>
>>> I have successfully exported the whole hierarchy via the following
>>> command, as stated in the docs (values were changed):
>>> *[dspace]/bin/dspace packager -d -a -t AIP -e ad...@myu.edu -i 4321/0
>>> sitewide-aip.zip*
>>>
>>> I have also successfully installed DSpace on the new location and have
>>> verified it is working. Now I need to restore the whole hierarchy using
>>> that sitewide-aip.zip
>>>
>>> I tried running the packager with all options available  [-s, -r
>>> (-k/-f)] but none work. The cmd just prints "ERROR: Package located at
>>> sitewide-aip.zip does not exist".
>>>
>>> Any help would be appreciated!
>>>
>>> --
>>> All messages to this mailing list should adhere to the Code of Conduct:
>>> https://duraspace.org/about/policies/code-of-conduct/
>>> ---
>>> You received this message because you are subscribed to the Google
>>> Groups "DSpace Technical Support" group.
>>> To unsubscribe from this group and stop receiving emails from it, send
>>> an email to dspace-tech...@googlegroups.com.
>>> To view this discussion on the web visit
>>> https://groups.google.com/d/msgid/dspace-tech/fe1b8862-aab6-49d4-b044-f931494042d7n%40googlegroups.com
>>> <https://groups.google.com/d/msgid/dspace-tech/fe1b8862-aab6-49d4-b044-f931494042d7n%40googlegroups.com?utm_medium=email_source=footer>
>>> .
>>>
>>
>>
>> --
>> At.te,
>>
>> José Geraldo
>>
>> --
> All messages to this mailing list should adhere to the Code of Conduct:
> https://duraspace.org/about/policies/code-of-conduct/
> ---
> You received this message because you are subscribed to the Google Groups
> "DSpace Technical Support" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to dspace-tech+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/dspace-tech/5aa1ea6c-40ce-418e-9e05-d396445e08dcn%40googlegroups.com
> <https://groups.google.com/d/msgid/dspace-tech/5aa1ea6c-40ce-418e-9e05-d396445e08dcn%40googlegroups.com?utm_medium=email_source=footer>
> .
>


-- 
At.te,

José Geraldo

-- 
All messages to this mailing list should adhere to the Code of Conduct: 
https://duraspace.org/about/policies/code-of-conduct/
--- 
You received this message because you are subscribed to the Google Groups 
"DSpace Technical Support" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to dspace-tech+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/dspace-tech/CANP4ikR5LcQ53QHjZyKE9ybYO2UphnPV659twPXZjB6jYd3ZrQ%40mail.gmail.com.

Re: [dspace-tech] Package located at site aip does not exist

[José Geraldo]

Hi,

Are you tried making a copy from database and from assetstore directory in
new instance?

Is this a migration option.

Em sáb., 13 de mar. de 2021 às 14:35, kpet  escreveu:

>
> Hello,
>
> I am using DSpace 6.3, and I am trying to move my DSpace installation from
> one pc to another.
>
> I have successfully exported the whole hierarchy via the following
> command, as stated in the docs (values were changed):
> *[dspace]/bin/dspace packager -d -a -t AIP -e ad...@myu.edu -i 4321/0
> sitewide-aip.zip*
>
> I have also successfully installed DSpace on the new location and have
> verified it is working. Now I need to restore the whole hierarchy using
> that sitewide-aip.zip
>
> I tried running the packager with all options available  [-s, -r (-k/-f)]
> but none work. The cmd just prints "ERROR: Package located at
> sitewide-aip.zip does not exist".
>
> Any help would be appreciated!
>
> --
> All messages to this mailing list should adhere to the Code of Conduct:
> https://duraspace.org/about/policies/code-of-conduct/
> ---
> You received this message because you are subscribed to the Google Groups
> "DSpace Technical Support" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to dspace-tech+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/dspace-tech/fe1b8862-aab6-49d4-b044-f931494042d7n%40googlegroups.com
> <https://groups.google.com/d/msgid/dspace-tech/fe1b8862-aab6-49d4-b044-f931494042d7n%40googlegroups.com?utm_medium=email_source=footer>
> .
>


-- 
At.te,

José Geraldo

-- 
All messages to this mailing list should adhere to the Code of Conduct: 
https://duraspace.org/about/policies/code-of-conduct/
--- 
You received this message because you are subscribed to the Google Groups 
"DSpace Technical Support" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to dspace-tech+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/dspace-tech/CANP4ikRrzxuM1MCFMgUUeBwhsULqZX%2Bfy1Kii8gyuHdto7uSVA%40mail.gmail.com.

Re: [dspace-tech] How to add rights to all collections and communities

[José Geraldo]

Hi,

This is can help you:
https://groups.google.com/g/dspace-tech/c/CL47srXLDko/m/8FGDQEUNAgAJ

Em qui., 11 de mar. de 2021 às 10:52, EPHRAIM MAKEKE <
make...@staff.msu.ac.zw> escreveu:

> Hello people
>
> Is there an easier way of providing rights to e-People to all the
> communities and collections at the same time instead of doing this one by
> one?
>
> Ephraim
>
> --
> All messages to this mailing list should adhere to the Code of Conduct:
> https://duraspace.org/about/policies/code-of-conduct/
> ---
> You received this message because you are subscribed to the Google Groups
> "DSpace Technical Support" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to dspace-tech+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/dspace-tech/4e8e9d75-7f86-4cfa-83e8-f0f584a67fban%40googlegroups.com
> <https://groups.google.com/d/msgid/dspace-tech/4e8e9d75-7f86-4cfa-83e8-f0f584a67fban%40googlegroups.com?utm_medium=email_source=footer>
> .
>


-- 
At.te,

José Geraldo

-- 
All messages to this mailing list should adhere to the Code of Conduct: 
https://duraspace.org/about/policies/code-of-conduct/
--- 
You received this message because you are subscribed to the Google Groups 
"DSpace Technical Support" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to dspace-tech+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/dspace-tech/CANP4ikTLiJuCE1HbZ6wF5qRkZjN1iABS70nXzdm3OYFMdhaHgA%40mail.gmail.com.

Re: F35 Change: "Fedora Linux" in /etc/os-release

[Geraldo Simião Kutz]

For me I go with your first suggestion:
Keep it simple for the OS, just fedora, as it already is; and for the
overall effort, Fedora Project. It works already.

Em qua, 10 de mar de 2021 09:27, Björn Persson 
escreveu:

> Vitaly Zaitsev via devel wrote:
> > 2. Why Linux and not GNU/Linux? Linux is just a kernel. GNU/Linux is an
> OS.
>
> It was very predictable that this argument would happen, and that's why
> I've been quite happy that Fedora is just "Fedora" with no "Linux" in
> the name.
>
> If we're going to name the distribution after some of its components,
> why stop at one or two? Arguably the most central part of any software
> distribution is its package manager. The programs that bring up the
> whole system are also rather important. And none of the GUI programs
> would exist without the windowing system so we need to mention X. Or
> should that honor go to Wayland now? Better give them equal treatment.
>
> "Fedora GNU/Linux/RPM/Python/DNF/SystemD/Xorg/Wayland/..."
>
> It's better to give the whole distribution its own name, and not name
> it after any of its components. Fedora is a software distribution. It
> contains Linux, many GNU components, RPM, MariaDB, Libreoffice and lots
> of other things, but its name is "Fedora". Or call it "Fedora Software
> Distribution" or anything else that doesn't single out any of the
> components. That approach seems to minimize the political fighting.
>
> Björn Persson
> ___
> devel mailing list -- devel@lists.fedoraproject.org
> To unsubscribe send an email to devel-le...@lists.fedoraproject.org
> Fedora Code of Conduct:
> https://docs.fedoraproject.org/en-US/project/code-of-conduct/
> List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
> List Archives:
> https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
> Do not reply to spam on the list, report it:
> https://pagure.io/fedora-infrastructure
>
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure

Re: [dspace-tech] Re: Index-Discovery with DSpace 5.8

[José Geraldo]

Using parameter -b, will return same error?

-b (re)build index, wiping out current one if it exists

Em sex., 5 de mar. de 2021 às 11:49, LBOV 
escreveu:

> Dealing with the same problem, any clues?
>
>
> On Thursday, February 25, 2021 at 2:25:34 AM UTC-6 Kosmas Kaifel wrote:
>
>> Hello
>>
>> with the command ../bin/dspace index-discovery I receive the following
>> error message
>>
>> Exception: Handle is null
>> org.dspace.discovery.SearchServiceException: Handle is null
>> at
>> org.dspace.discovery.SolrServiceImpl.cleanIndex(SolrServiceImpl.java:507)
>> at org.dspace.discovery.IndexClient.main(IndexClient.java:126)
>> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>> at
>> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
>>
>> at
>> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>>
>> at java.lang.reflect.Method.invoke(Method.java:498)
>> at
>> org.dspace.app.launcher.ScriptLauncher.runOneCommand(ScriptLauncher.java:226)
>>
>> at
>> org.dspace.app.launcher.ScriptLauncher.main(ScriptLauncher.java:78)
>> Caused by: java.lang.IllegalArgumentException: Handle is null
>> at
>> org.dspace.handle.HandleManager.findHandleInternal(HandleManager.java:532)
>>
>> at
>> org.dspace.handle.HandleManager.resolveToObject(HandleManager.java:322)
>> at
>> org.dspace.discovery.SolrServiceImpl.cleanIndex(SolrServiceImpl.java:488)
>> ... 7 more
>> SOLR Search Optimize -- Process Started:1614200413002
>> SOLR Search Optimize -- Process Finished:1614200413017
>> SOLR Search Optimize -- Total time taken:15 (ms).
>>
>> With two sql-statment I try to find items without handle but I can not
>> find any
>>
>> 1) select * from handle h where h.handle='' or h.handle is null
>>
>> 2) Select i.item_id FROM item i WHERE i.in_archive=True And Not EXISTS
>> (Select resource_id FROM handle h WHERE h.resource_id = i.item_id
>> And h.resource_type_id = 2)
>>
>> Best Regards
>> Kosmas
>>
>> --
>> +---+
>> Universität Ulm
>> Kommunikations- und Informationszentrum (kiz)
>> Abt. Informationsmedien
>> Albert-Einstein-Allee 37
>> 89081 Ulm
>> Tel. 0731/50-15495
>> EMail: kosmas...@uni-ulm.de
>> ++
>>
>> --
> All messages to this mailing list should adhere to the Code of Conduct:
> https://duraspace.org/about/policies/code-of-conduct/
> ---
> You received this message because you are subscribed to the Google Groups
> "DSpace Technical Support" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to dspace-tech+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/dspace-tech/e0d7ce34-70f2-4f08-8ca8-3e8dcb67d944n%40googlegroups.com
> <https://groups.google.com/d/msgid/dspace-tech/e0d7ce34-70f2-4f08-8ca8-3e8dcb67d944n%40googlegroups.com?utm_medium=email_source=footer>
> .
>


-- 
At.te,

José Geraldo

-- 
All messages to this mailing list should adhere to the Code of Conduct: 
https://duraspace.org/about/policies/code-of-conduct/
--- 
You received this message because you are subscribed to the Google Groups 
"DSpace Technical Support" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to dspace-tech+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/dspace-tech/CANP4ikTP2bXKFgU4dQh7nzaWny3a9BVPnV%2B0vQw197wZqtVoNg%40mail.gmail.com.

Re: [dspace-tech] ANT FRESH_INSTALL GIVES ERROR

[José Geraldo]

Verify Dabase Setup of Dspace installation's:
https://wiki.lyrasis.org/display/DSDOC6x/Installing+DSpace#InstallingDSpace-Installation

You MUST enable the pgcrypto extension
<http://www.postgresql.org/docs/9.4/static/pgcrypto.html> on your new
dspace database.  Again, this can only be enabled by a "superuser" account
(e.g. postgres)
# Login to the database as a superuser, and enable the pgcrypto extension
on this database
psql --username=postgres dspace -c "CREATE EXTENSION pgcrypto;"

Em sex., 5 de mar. de 2021 às 11:49, Erick Olotu 
escreveu:

> Hi Erveryone
>
> i am installatiing dspace in windows 10 computer, all steps i follwed were
> succeeded except when i start installing dspace using command ant
> fresh_install it returns error as following
> Plaese any assistance on fixing this issue
> Buildfile:
> C:\dspace\DSpace-dspace-6.3\DSpace-dspace-6.3\dspace\target\dspace-installer\build.xml
>
> init_installation:
>
> prepare_configs:
> [mkdir] Created dir:
> C:\dspace\DSpace-dspace-6.3\DSpace-dspace-6.3\dspace\target\dspace-installer\config-temp
>  [copy] Copying 159 files to
> C:\dspace\DSpace-dspace-6.3\DSpace-dspace-6.3\dspace\target\dspace-installer\config-temp
>  [copy] Copying 1 file to
> C:\dspace\DSpace-dspace-6.3\DSpace-dspace-6.3\dspace\target\dspace-installer\config-temp
>  [copy] Copying 16 files to
> C:\dspace\DSpace-dspace-6.3\DSpace-dspace-6.3\dspace\target\dspace-installer\config-temp
>
> init_configs:
>  [copy] Copying 1 file to C:\dspace\config
>[delete] Deleting directory
> C:\dspace\DSpace-dspace-6.3\DSpace-dspace-6.3\dspace\target\dspace-installer\config-temp
>
> test_database:
>  [java] 2021-03-05 16:53:42,361 WARN
> org.dspace.services.email.EmailServiceImpl @ Couldn't get an email session
> from environment:  Need to specify class name in environment or system
> property, or as an applet parameter, or in an application resource file:
> java.naming.factory.initial
>  [java]
>  [java] Attempting to connect to database
>  [java] Connected successfully!
>  [java]
>  [java] Database Type: postgres
>  [java] Database URL: jdbc:postgresql://localhost:5432/dspace
>  [java] Database Schema: public
>  [java] Database Username: dspace
>  [java] Database Software: PostgreSQL version 10.16
>  [java] Database Driver: PostgreSQL JDBC Driver version 42.2.1
>  [java] PostgreSQL 'pgcrypto' extension installed/up-to-date? false
> (not installed)
>  [java]
>  [java] WARNING: Required PostgreSQL 'pgcrypto' extension is NOT
> INSTALLED on this database.
>  [java]
>  [java] ** DSpace REQUIRES PostgreSQL >= 9.4 AND pgcrypto extension >=
> 1.1 **
>  [java]
>  [java] To install it, please connect to your DSpace database as a
> 'superuser' and manually run the following command:
>  [java]
>  [java]   CREATE EXTENSION pgcrypto;
>  [java]
>  [java] 2021-03-05 16:53:43,459 WARN
> org.dspace.services.sessions.SessionRequestServiceImpl @ Request
> interceptor
> (org.dspace.services.events.SystemEventService$EventRequestInterceptor@46093133)
> failed to execute on end (request-532-1614952422699): null
>
> BUILD FAILED
> C:\dspace\DSpace-dspace-6.3\DSpace-dspace-6.3\dspace\target\dspace-installer\build.xml:789:
> Java returned: 1
>
> Total time: 15 seconds
>
> --
> All messages to this mailing list should adhere to the Code of Conduct:
> https://duraspace.org/about/policies/code-of-conduct/
> ---
> You received this message because you are subscribed to the Google Groups
> "DSpace Technical Support" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to dspace-tech+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/dspace-tech/39bf1aa9-6f9a-447e-ac6d-99f575ae71f7n%40googlegroups.com
> <https://groups.google.com/d/msgid/dspace-tech/39bf1aa9-6f9a-447e-ac6d-99f575ae71f7n%40googlegroups.com?utm_medium=email_source=footer>
> .
>


-- 
At.te,

José Geraldo

-- 
All messages to this mailing list should adhere to the Code of Conduct: 
https://duraspace.org/about/policies/code-of-conduct/
--- 
You received this message because you are subscribed to the Google Groups 
"DSpace Technical Support" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to dspace-tech+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/dspace-tech/CANP4ikSr4Lq4C_06LgMEgzOLLaCMzsx%3DdYuc__%3D9nx_EGv_yoA%40mail.gmail.com.

Re: [dspace-tech] Multilingual support document type translation

[José Geraldo]

Hi,

After change, is necessary re-build code and restart Tomcat.

Em qua., 3 de mar. de 2021 às 11:16, István Molnár 
escreveu:

>
> I use DSpace 6.3 jspui with 3 languages. It works mainly, but when I open
> a single item the document type cannot be translated. I tried to add
> metadata.dc.type.animation = Animation, for example, to all languages(with
> the correct values) but nothing changes.
>
> --
> All messages to this mailing list should adhere to the Code of Conduct:
> https://duraspace.org/about/policies/code-of-conduct/
> ---
> You received this message because you are subscribed to the Google Groups
> "DSpace Technical Support" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to dspace-tech+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/dspace-tech/691317d6-f607-403d-afdf-4660b0295db2n%40googlegroups.com
> <https://groups.google.com/d/msgid/dspace-tech/691317d6-f607-403d-afdf-4660b0295db2n%40googlegroups.com?utm_medium=email_source=footer>
> .
>


-- 
At.te,

José Geraldo

-- 
All messages to this mailing list should adhere to the Code of Conduct: 
https://duraspace.org/about/policies/code-of-conduct/
--- 
You received this message because you are subscribed to the Google Groups 
"DSpace Technical Support" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to dspace-tech+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/dspace-tech/CANP4ikQJVYN2%2BeU5gJu2ABFUKgzTYeRYDEXr3s8XHzD7r6A96w%40mail.gmail.com.

Re: [Freedos-devel] FreeDOS as a unikernel?

[Geraldo Netto]

Hi Pablo/Eric/All,

I guess there are many different strategies to handle it
But maybe what you're looking for is a customized version of dosemu
(http://www.dosemu.org)?
It seems that usually, unikernels are some sort of "container" or
application-oriented operating system
(https://www.lisha.ufsc.br/pub/Frohlich_2001.pdf) in the sense that
you embed a single application together with the kernel (single
address space operating system with just enough
drivers/infrastructure)


Kind Regards,

Geraldo Netto
site: http://exdev.sf.net
github: https://github.com/geraldo-netto
linkedin: https://www.linkedin.com/in/geraldonetto
facebook: https://web.facebook.com/geraldo.netto.161

On Mon, 1 Mar 2021 at 20:28, Pablo Pessolani  wrote:
>
> Thanks Eric.
> I am not thinking in running binary DOS applications which use the real mode.
> I am thinking in source code applications built (compiled) on linux but 
> instead of linked with libc library, they should be linked to a new "libdosc" 
> library which use the FreeDOS system calls and environment.
> It would be a linux executable binary file.
> Regards.
> PAP
>
> 
> De: Eric Auer 
> Enviado: lunes, 1 de marzo de 2021 15:52
> Para: freedos-devel@lists.sourceforge.net 
> 
> Asunto: Re: [Freedos-devel] FreeDOS as a unikernel?
>
>
> Hi PAP,
>
> I assume unikernel means replacing hardware I/O by
> calls to a suitable hypervisor interface? In a way,
> DOS already does that by using BIOS. So you could
> make a BIOS-Unikernel and then run FreeDOS as app
> on that. But how do you deal with the fact that a
> DOS kernel and DOS apps will prefer a DOS memory
> model with real mode compatible pointers, can the
> hypervisor offer such spaces?
>
> Regards, Eric
>
>
>
> > Hi Guys.
> >   I am working on several unikernels on Linux
> > (not over QEMU, KVM, XEN or any other emulator/
> > hypervisor) using Linux system calls and the
> > virtualization facilities offered by the Linux kernel.
>
> >  Would there be any interest in modifying freedos
> > so that it can run on Linux and its virtual devices
> > instead of running on real hardware (as User Mode Linux does) ?
> > Regards.
> > PAP
>
>
>
> ___
> Freedos-devel mailing list
> Freedos-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/freedos-devel
> ___
> Freedos-devel mailing list
> Freedos-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/freedos-devel


___
Freedos-devel mailing list
Freedos-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-devel

Re: [dspace-tech] Checking number of documents in each community

[José Geraldo]

Hi,

In dspace.cfg there is setting named webui.strengths.show.

https://github.com/DSpace/DSpace/blob/80c3f98447dfe1ca6977faebb774ac406532a29e/dspace/config/dspace.cfg#L976

# Settings for item count (strength) information 

# Whether to display collection and community strengths (i.e. item counts)
# XMLUI only makes strengths available to themes if this is set to true!
# To show strengths in the XMLUI, you also need to create or use a theme
which
# displays them.
webui.strengths.show = false



Em sex., 26 de fev. de 2021 às 11:54, EPHRAIM MAKEKE <
make...@staff.msu.ac.zw> escreveu:

> Hello people
>
> Is there an easy way of checking the number of documents in each
> community. Sorry I have started using Dspace after a long time.
>
> --
> All messages to this mailing list should adhere to the DuraSpace Code of
> Conduct: https://duraspace.org/about/policies/code-of-conduct/
> ---
> You received this message because you are subscribed to the Google Groups
> "DSpace Technical Support" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to dspace-tech+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/dspace-tech/181cd95b-1c6a-4024-bb36-706940842ba9n%40googlegroups.com
> <https://groups.google.com/d/msgid/dspace-tech/181cd95b-1c6a-4024-bb36-706940842ba9n%40googlegroups.com?utm_medium=email_source=footer>
> .
>


-- 
At.te,

José Geraldo

-- 
All messages to this mailing list should adhere to the DuraSpace Code of 
Conduct: https://duraspace.org/about/policies/code-of-conduct/
--- 
You received this message because you are subscribed to the Google Groups 
"DSpace Technical Support" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to dspace-tech+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/dspace-tech/CANP4ikSXNmWuCv8xT2gyFr9cCo%2BEEhD-czxVT%2Bq7qk4nLijvKg%40mail.gmail.com.

Re: Installation summary screen at F34 spins doesn't show anymore the option to change Network and Host names

[Geraldo Simião Kutz]

Radek Vykydal (rvyky...@redhat.com) said on the devel list that this
seems to be a fallout of
https://github.com/rhinstaller/anaconda/commit/6b80b7b33c312faa69c22e4bdfe758f186d32786
and oriented me to open this ticket and set it with F34 Beta freeze
exception request.

So, how do we set a Beta freeze exception request?


Em qui., 25 de fev. de 2021 às 10:38, Geraldo Simião Kutz <
geraldo.simiao.k...@gmail.com> escreveu:

> I opened this BZ ticket:
> https://bugzilla.redhat.com/show_bug.cgi?id=1932961
>
___
test mailing list -- test@lists.fedoraproject.org
To unsubscribe send an email to test-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/test@lists.fedoraproject.org
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure

Installation summary screen at F34 spins doesn't show anymore the option to change Network and Host names

[Geraldo Simião Kutz]

I opened this BZ ticket: https://bugzilla.redhat.com/show_bug.cgi?id=1932961
___
test mailing list -- test@lists.fedoraproject.org
To unsubscribe send an email to test-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/test@lists.fedoraproject.org
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure

Re: Changes on the installation summary screen at anaconda for F34 spins

[Geraldo Simião Kutz]

Ticket opened:
https://bugzilla.redhat.com/show_bug.cgi?id=1932961

Em ter., 23 de fev. de 2021 às 11:51, Radek Vykydal 
escreveu:

> Hello,
>
> this seems to be a fallout of
> https://github.com/rhinstaller/anaconda/commit/6b80b7b33c312faa69c22e4bdfe758f186d32786
> .
>
> We should be able to fix it to bring the F33 behavior back for the spins,
> but we'd need a Bugzilla ticket opened for it, ideally with F34 Beta freeze
> exception request.
>
> Could you please open the BZ ticket?
>
> Thank you,
>
> Radek
>
> Anaconda team
>
> On 2/22/21 8:24 PM, Geraldo Simião Kutz wrote:
>
> Hello friends,
>
> Since the ISO images for the F34 spins where ready I noticed something
> different on the anaconda procedures to installation: on the installation
> summary screen it doesn't show anymore the option to change Network and
> Host name, as it does on the F33 and earlier versions. I saw this on kde
> spin and xfce spin too. Now, on F34 it installs with the default "fedora"
> host name, and if you wanna change it you must do it after installation,
> with the command "hostnamectl set-hostname".
> Is that expected? I missed some announcement regarding this change?
> I send attached some screenshots from anaconda for the F33 and F34 kde and
> xfce spins...
>
> Best regards
>
> Geraldo
>
> FAS / IRC / Telegram: *geraldosimiao*
>
>
> ___
> test mailing list -- test@lists.fedoraproject.org
> To unsubscribe send an email to test-le...@lists.fedoraproject.org
> Fedora Code of Conduct: 
> https://docs.fedoraproject.org/en-US/project/code-of-conduct/
> List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
> List Archives: 
> https://lists.fedoraproject.org/archives/list/test@lists.fedoraproject.org
> Do not reply to spam on the list, report it: 
> https://pagure.io/fedora-infrastructure
>
> ___
> test mailing list -- test@lists.fedoraproject.org
> To unsubscribe send an email to test-le...@lists.fedoraproject.org
> Fedora Code of Conduct:
> https://docs.fedoraproject.org/en-US/project/code-of-conduct/
> List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
> List Archives:
> https://lists.fedoraproject.org/archives/list/test@lists.fedoraproject.org
> Do not reply to spam on the list, report it:
> https://pagure.io/fedora-infrastructure
>
___
test mailing list -- test@lists.fedoraproject.org
To unsubscribe send an email to test-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/test@lists.fedoraproject.org
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure

Re: Changes on the installation summary screen at anaconda for F34 spins

[Geraldo Simião Kutz]

Hi, only today I came to see your answer, sorry for been late.
Yes I can open a BZ ticket for that

Thanks

Em ter., 23 de fev. de 2021 às 11:51, Radek Vykydal 
escreveu:

> Hello,
>
> this seems to be a fallout of
> https://github.com/rhinstaller/anaconda/commit/6b80b7b33c312faa69c22e4bdfe758f186d32786
> .
>
> We should be able to fix it to bring the F33 behavior back for the spins,
> but we'd need a Bugzilla ticket opened for it, ideally with F34 Beta freeze
> exception request.
>
> Could you please open the BZ ticket?
>
> Thank you,
>
> Radek
>
> Anaconda team
>
> On 2/22/21 8:24 PM, Geraldo Simião Kutz wrote:
>
> Hello friends,
>
> Since the ISO images for the F34 spins where ready I noticed something
> different on the anaconda procedures to installation: on the installation
> summary screen it doesn't show anymore the option to change Network and
> Host name, as it does on the F33 and earlier versions. I saw this on kde
> spin and xfce spin too. Now, on F34 it installs with the default "fedora"
> host name, and if you wanna change it you must do it after installation,
> with the command "hostnamectl set-hostname".
> Is that expected? I missed some announcement regarding this change?
> I send attached some screenshots from anaconda for the F33 and F34 kde and
> xfce spins...
>
> Best regards
>
> Geraldo
>
> FAS / IRC / Telegram: *geraldosimiao*
>
>
> ___
> test mailing list -- test@lists.fedoraproject.org
> To unsubscribe send an email to test-le...@lists.fedoraproject.org
> Fedora Code of Conduct: 
> https://docs.fedoraproject.org/en-US/project/code-of-conduct/
> List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
> List Archives: 
> https://lists.fedoraproject.org/archives/list/test@lists.fedoraproject.org
> Do not reply to spam on the list, report it: 
> https://pagure.io/fedora-infrastructure
>
> ___
> test mailing list -- test@lists.fedoraproject.org
> To unsubscribe send an email to test-le...@lists.fedoraproject.org
> Fedora Code of Conduct:
> https://docs.fedoraproject.org/en-US/project/code-of-conduct/
> List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
> List Archives:
> https://lists.fedoraproject.org/archives/list/test@lists.fedoraproject.org
> Do not reply to spam on the list, report it:
> https://pagure.io/fedora-infrastructure
>
___
test mailing list -- test@lists.fedoraproject.org
To unsubscribe send an email to test-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/test@lists.fedoraproject.org
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure

Re: Donate 1 minute of your time to test upgrades from F33 to F34

[Geraldo Simião Kutz]

I tried here on a F33 kde spin (on bare metal Acer/intel notebook) and it
worked fine, just as expected:
Instalar48 Pacotes
Atualizar 2019 Pacotes
Remover  5 Pacotes
Desatualizar 2 Pacotes
Tamanho total do download: 1.8 G

regards
Geraldo

FAS: geraldosimiao


Em sáb., 20 de fev. de 2021 às 06:49, Miroslav Suchý 
escreveu:

> Do you want to make Fedora 34 better? Please spend 1 minute of your time
> and try to run:
>
># Run this only if you use default Fedora modules
># next time you run any DNF command default modules will be enabled
> again
>sudo dnf module reset '*'
>
>sudo dnf --releasever=34 --setopt=module_platform_id=platform:f34 \
>  --enablerepo=updates-testing --enablerepo=updates-testing-modular \
>  distro-sync
>
> This command does not replace `dnf system-upgrade`, but it will reveal
> potential problems. You may also run `dnf
> upgrade` before running this command.
>
> If you have have rdma-core.i686 installed you have to pass
> `--allowerasing`.
> https://bugzilla.redhat.com/show_bug.cgi?id=1919864
>
>
> If you get this prompt:
>
>...
>Total download size: XXX M
>Is this ok [y/N]:
>
> you can answer N and nothing happens, no need to test the actual upgrade.
>
> But very likely you get some dependency problem now. In that case, please
> report it against the appropriate package. Or
> against fedora-obsolete-packages if that package should be removed in
> Fedora 34. Please check existing reports against
> fedora-obsolete-packages first:
>https://red.ht/2kuBDPu
> and also there is already bunch of "Fails to install" reports:
>https://bugzilla.redhat.com/show_bug.cgi?id=F34FailsToInstall
>
> Thank you
>
> P.S. sent from workstation successfully upgraded to F34 :)
>
> --
> Miroslav Suchy, RHCA
> Red Hat, Associate Manager, Community Packaging Tools, #brno,
> #fedora-buildsys
> ___
> devel mailing list -- devel@lists.fedoraproject.org
> To unsubscribe send an email to devel-le...@lists.fedoraproject.org
> Fedora Code of Conduct:
> https://docs.fedoraproject.org/en-US/project/code-of-conduct/
> List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
> List Archives:
> https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
> Do not reply to spam on the list, report it:
> https://pagure.io/fedora-infrastructure
>
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure

Re: [Freedos-user] FreeDOS Virtual Get-together

[Geraldo Netto]

Hi folks!

Is it still happening?


Geraldo Netto
site: http://exdev.sf.net
github: https://github.com/geraldo-netto
linkedin: https://www.linkedin.com/in/geraldonetto
facebook: https://web.facebook.com/geraldo.netto.161

On Sun, 21 Feb 2021 at 18:06, Jim Hall  wrote:
>
> Join us for the next hour or so, in the FreeDOS Virtual Get-Together! You can 
> connect for free directly from any modern web browser, or using the BlueJeans 
> Meetings client.
>
>
> https://bluejeans.com/117827007
>
> ___
> Freedos-user mailing list
> Freedos-user@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/freedos-user


___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user

Re: Self-introduction: Josevaldo

[Geraldo Simião Kutz]

Does anyone with sponsorship level apply to sponsor josevaldo?


Em seg, 1 de fev de 2021 08:25, josevaldo da rocha santos <
joseva...@fedoraproject.org> escreveu:

> Hi all,
>
> All right? I'm Josevaldo Santos, Brazilian. I intend to be able to
> collaborate with fedora, assisting in the tests.
> I currently use the F33, in dual boot.
>
> I can say that I am new to linux, reinstalled on my pc a little over 9
> months, but around 2005 I used it a lot when supporting internet providers,
> installing and configuring firewall, webcache, bandwidth control and other
> things, always remotely.
>
> That's it, I intend to learn and collaborate more actively with the
> project.
> ___
> test mailing list -- test@lists.fedoraproject.org
> To unsubscribe send an email to test-le...@lists.fedoraproject.org
> Fedora Code of Conduct:
> https://docs.fedoraproject.org/en-US/project/code-of-conduct/
> List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
> List Archives:
> https://lists.fedoraproject.org/archives/list/test@lists.fedoraproject.org
>
___
test mailing list -- test@lists.fedoraproject.org
To unsubscribe send an email to test-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/test@lists.fedoraproject.org
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure

Re: [dspace-tech] Restrict access to logged-in users only

[José Geraldo]

Very good.

Needing can send email: josg...@gmail.com

Em sex., 12 de fev. de 2021 às 10:54, Sean Carte 
escreveu:

> Thanks yet again, José! After much testing, I was able to modify the
> rights to all items in the repository. I would not have been able to get
> this right without your assistance.
>
> On Wed, 3 Feb 2021 at 17:58, José Geraldo  wrote:
>
>> Use the database to change or add permission.
>>
>> The table used is resourcepolicy.
>>
>> Updating the epersongroup_id to id of the special group created e o
>> filtro por action_id.
>>
>> action_id:
>>
>> 0 read
>> 1 write
>> 3 add
>> 4 remove
>> 9 default_bitstream_read
>> 10 default_item_read
>> 11 admin
>>
>> Em qua., 3 de fev. de 2021 às 11:52, Sean Carte 
>> escreveu:
>>
>>> I was hoping for some guidance on that. I did look at the tables, but
>>> wasn't able to find anything obviously related to access rights.
>>>
>>> Or did you mean that I should use the database to move items from the
>>> collection? That might work.
>>>
>>> On Wed, 3 Feb 2021 at 15:11, José Geraldo  wrote:
>>>
>>>> Another option would be to backup your database and make changes to the
>>>> database.
>>>>
>>>> Em qua., 3 de fev. de 2021 às 04:13, Sean Carte 
>>>> escreveu:
>>>>
>>>>> For most collections, using the wildcard policy admin tool has worked
>>>>> very well, and I have been able to restrict their bitstreams to logged-in
>>>>> users. However, I have two collections with over 1000 items. For one of
>>>>> these, with 1688 items, I was not able to remove the anonymous read 
>>>>> access;
>>>>> the browser reports an internal error, but there's nothing in the tomcat 
>>>>> or
>>>>> dspace logs. Another collection, of 1012 items, allowed me to remove
>>>>> anonymous read access, but I have not been able to add READ access for the
>>>>> logged-in group.
>>>>>
>>>>> Apart from moving hundreds of items out of those collections, to
>>>>> reduce their size, does anybody have any suggestions on how I should
>>>>> proceed?
>>>>>
>>>>> DSpace version:  6.3
>>>>> XMLUI
>>>>> Mirage2 theme
>>>>>
>>>>> On Fri, 29 Jan 2021 at 20:48, Sean Carte  wrote:
>>>>>
>>>>>> Thanks again, José; you've been extremely helpful.
>>>>>>
>>>>>> On Fri, 29 Jan 2021 at 15:43, José Geraldo  wrote:
>>>>>>
>>>>>>> Hi,
>>>>>>>
>>>>>>> Items accepted in a collection inherit the associated authorization
>>>>>>> policies DEFAULT_ITEM_READ and DEFAULT_BITSTREAM_READ, which become READ
>>>>>>> policies for the item and its attachments.
>>>>>>>
>>>>>>> However, when changing the default policies for a collection, once
>>>>>>> items are accepted, the policies for existing items will not be changed
>>>>>>> automatically.
>>>>>>>
>>>>>>> Soon, a user, without logging in and in possession of the link to
>>>>>>> one of the items in the collection, will have access to the item and its
>>>>>>> contents.
>>>>>>>
>>>>>>> To get around this point, you will need to change the permissions of
>>>>>>> the items in the collection using the Policy Administration Tool to make
>>>>>>> them accessible only to logged-in users.
>>>>>>>
>>>>>>> For each item in a collection, there is only one READ policy
>>>>>>> configured for the Anonymous group.
>>>>>>>
>>>>>>> However, the tool does not have the option to edit policies, having
>>>>>>> only the options to add and delete policies.
>>>>>>>
>>>>>>> Therefore, it will be necessary to first delete the policies for
>>>>>>> items and binary files (attachments) and then create new READ policies
>>>>>>> linked to the special group for them.
>>>>>>>
>>>>>>> This process is done one collection at a time, if you need to apply
>>>>>>> to all collections, a suggestion would be to apply it to the database.
>>

Re: [dspace-tech] MvN Package error

[José Geraldo]

Hi,

Git is installed?

https://wiki.lyrasis.org/display/DSDOC6x/Installing+DSpace#InstallingDSpace-Git(codeversioncontrol)

Em sex., 12 de fev. de 2021 às 11:51, kamlesh vegad 
escreveu:

> Dear All,
> I install DSpace 6.3 in windows 10 64bit OS at the time install Mvn
> package that show error
> Kindly help to solve below error
>
> [ERROR] Failed to execute goal
> org.codehaus.mojo:buildnumber-maven-plugin:1.4:create (default) on project
> dspace-api: Cannot get the revision information from the scm repository :
> [ERROR] Exception while executing SCM command. Error while executing
> command. Error while executing process. Cannot run program "git" (in
> directory "C:\dspace-6.3-src-release\dspace-api"): CreateProcess error=2,
> The system cannot find the file specified
> [ERROR] -> [Help 1]
> [ERROR]
> [ERROR] To see the full stack trace of the errors, re-run Maven with the
> -e switch.
> [ERROR] Re-run Maven using the -X switch to enable full debug logging.
> [ERROR]
> [ERROR] For more information about the errors and possible solutions,
> please read the following articles:
> [ERROR] [Help 1]
> http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException
> [ERROR]
> [ERROR] After correcting the problems, you can resume the build with the
> command
> [ERROR]   mvn  -rf :dspace-api
>
>
> with regards,
>
>
> --
> All messages to this mailing list should adhere to the DuraSpace Code of
> Conduct: https://duraspace.org/about/policies/code-of-conduct/
> ---
> You received this message because you are subscribed to the Google Groups
> "DSpace Technical Support" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to dspace-tech+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/dspace-tech/6aab169a-8bca-4ae2-ab9b-4f3c319e1c74n%40googlegroups.com
> <https://groups.google.com/d/msgid/dspace-tech/6aab169a-8bca-4ae2-ab9b-4f3c319e1c74n%40googlegroups.com?utm_medium=email_source=footer>
> .
>


-- 
At.te,

José Geraldo

-- 
All messages to this mailing list should adhere to the DuraSpace Code of 
Conduct: https://duraspace.org/about/policies/code-of-conduct/
--- 
You received this message because you are subscribed to the Google Groups 
"DSpace Technical Support" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to dspace-tech+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/dspace-tech/CANP4ikQu4ESyAyELqEA3vSamjS-ioXYEDvAYEd12t6Lyu5YgoQ%40mail.gmail.com.

Re: Fedora SOAS 33 Beta Startup Goes Straight to Login Screen

[Geraldo Simião Kutz]

I tried the last respin now, from 2021-01-29.
And it starts normaly, without any bugs (
https://dl.fedoraproject.org/pub/alt/live-respins/F33-SOAS-x86_64-LIVE-20210129.iso
)


Em seg., 26 de out. de 2020 às 09:04, Chihurumnaya Ibiam <
ibiamchihurumn...@gmail.com> escreveu:

> Tried logging in with "liveuser" without any password and I get an
> "Incorrect password, please try again" error.
> ___
> test mailing list -- test@lists.fedoraproject.org
> To unsubscribe send an email to test-le...@lists.fedoraproject.org
> Fedora Code of Conduct:
> https://docs.fedoraproject.org/en-US/project/code-of-conduct/
> List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
> List Archives:
> https://lists.fedoraproject.org/archives/list/test@lists.fedoraproject.org
>
___
test mailing list -- test@lists.fedoraproject.org
To unsubscribe send an email to test-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/test@lists.fedoraproject.org

Re: Fedora SOAS 33 Beta Startup Goes Straight to Login Screen

[Geraldo Simião Kutz]

This bug still on.
Here's the ticket: https://bugzilla.redhat.com/show_bug.cgi?id=1895184

Em seg., 26 de out. de 2020 às 09:04, Chihurumnaya Ibiam <
ibiamchihurumn...@gmail.com> escreveu:

> Tried logging in with "liveuser" without any password and I get an
> "Incorrect password, please try again" error.
> ___
> test mailing list -- test@lists.fedoraproject.org
> To unsubscribe send an email to test-le...@lists.fedoraproject.org
> Fedora Code of Conduct:
> https://docs.fedoraproject.org/en-US/project/code-of-conduct/
> List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
> List Archives:
> https://lists.fedoraproject.org/archives/list/test@lists.fedoraproject.org
>
___
test mailing list -- test@lists.fedoraproject.org
To unsubscribe send an email to test-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/test@lists.fedoraproject.org

Re: [dspace-tech] customize the simple item view

[José Geraldo]

This can help you:
https://github.com/DSpace/DSpace/blob/dspace-6.3/dspace/config/dspace.cfg#L1591

Use the webui.itemdisplay.default.

Em sex., 5 de fev. de 2021 às 04:16, Massimiliano CILURZO 
escreveu:

> Dear All,
>   We have Dspace 6.3 with the Mirage 2 Theme, we would like to customize
> the simple item view and add som dc fields.
> How we can do this?
> Thanks
> Best regards
> Massimiliano
>
> --
> All messages to this mailing list should adhere to the DuraSpace Code of
> Conduct: https://duraspace.org/about/policies/code-of-conduct/
> ---
> You received this message because you are subscribed to the Google Groups
> "DSpace Technical Support" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to dspace-tech+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/dspace-tech/3b0f00cf-49f5-4924-90bd-4e0eb616c0c4n%40googlegroups.com
> <https://groups.google.com/d/msgid/dspace-tech/3b0f00cf-49f5-4924-90bd-4e0eb616c0c4n%40googlegroups.com?utm_medium=email_source=footer>
> .
>


-- 
At.te,

José Geraldo

-- 
All messages to this mailing list should adhere to the DuraSpace Code of 
Conduct: https://duraspace.org/about/policies/code-of-conduct/
--- 
You received this message because you are subscribed to the Google Groups 
"DSpace Technical Support" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to dspace-tech+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/dspace-tech/CANP4ikQN6aKaL-1WRLAyk9yiYsYEEHmcybPTaVM8NC8ijHVtbQ%40mail.gmail.com.

Re: [dspace-tech] Restrict access to logged-in users only

[José Geraldo]

Use the database to change or add permission.

The table used is resourcepolicy.

Updating the epersongroup_id to id of the special group created e o filtro
por action_id.

action_id:

0 read
1 write
3 add
4 remove
9 default_bitstream_read
10 default_item_read
11 admin

Em qua., 3 de fev. de 2021 às 11:52, Sean Carte 
escreveu:

> I was hoping for some guidance on that. I did look at the tables, but
> wasn't able to find anything obviously related to access rights.
>
> Or did you mean that I should use the database to move items from the
> collection? That might work.
>
> On Wed, 3 Feb 2021 at 15:11, José Geraldo  wrote:
>
>> Another option would be to backup your database and make changes to the
>> database.
>>
>> Em qua., 3 de fev. de 2021 às 04:13, Sean Carte 
>> escreveu:
>>
>>> For most collections, using the wildcard policy admin tool has worked
>>> very well, and I have been able to restrict their bitstreams to logged-in
>>> users. However, I have two collections with over 1000 items. For one of
>>> these, with 1688 items, I was not able to remove the anonymous read access;
>>> the browser reports an internal error, but there's nothing in the tomcat or
>>> dspace logs. Another collection, of 1012 items, allowed me to remove
>>> anonymous read access, but I have not been able to add READ access for the
>>> logged-in group.
>>>
>>> Apart from moving hundreds of items out of those collections, to reduce
>>> their size, does anybody have any suggestions on how I should proceed?
>>>
>>> DSpace version:  6.3
>>> XMLUI
>>> Mirage2 theme
>>>
>>> On Fri, 29 Jan 2021 at 20:48, Sean Carte  wrote:
>>>
>>>> Thanks again, José; you've been extremely helpful.
>>>>
>>>> On Fri, 29 Jan 2021 at 15:43, José Geraldo  wrote:
>>>>
>>>>> Hi,
>>>>>
>>>>> Items accepted in a collection inherit the associated authorization
>>>>> policies DEFAULT_ITEM_READ and DEFAULT_BITSTREAM_READ, which become READ
>>>>> policies for the item and its attachments.
>>>>>
>>>>> However, when changing the default policies for a collection, once
>>>>> items are accepted, the policies for existing items will not be changed
>>>>> automatically.
>>>>>
>>>>> Soon, a user, without logging in and in possession of the link to one
>>>>> of the items in the collection, will have access to the item and its
>>>>> contents.
>>>>>
>>>>> To get around this point, you will need to change the permissions of
>>>>> the items in the collection using the Policy Administration Tool to make
>>>>> them accessible only to logged-in users.
>>>>>
>>>>> For each item in a collection, there is only one READ policy
>>>>> configured for the Anonymous group.
>>>>>
>>>>> However, the tool does not have the option to edit policies, having
>>>>> only the options to add and delete policies.
>>>>>
>>>>> Therefore, it will be necessary to first delete the policies for items
>>>>> and binary files (attachments) and then create new READ policies linked to
>>>>> the special group for them.
>>>>>
>>>>> This process is done one collection at a time, if you need to apply to
>>>>> all collections, a suggestion would be to apply it to the database.
>>>>>
>>>>> Em sex., 29 de jan. de 2021 às 04:09, Sean Carte 
>>>>> escreveu:
>>>>>
>>>>>> Using the login.specialgroup, along with removing default read access
>>>>>> to the collections, does restrict access to collections listed on the 
>>>>>> home
>>>>>> page. However, anonymous access is still available to items made 
>>>>>> available
>>>>>> by Discovery. That is, in the 'Recently Added' section, or via search, or
>>>>>> the browse lists.
>>>>>>
>>>>>> Removing anonymous read access from items' bitstreams and replacing
>>>>>> it with read access for the authenticated special group does work, but 
>>>>>> I'm
>>>>>> going to have to repeat this process every time a new item is added. 
>>>>>> Also,
>>>>>> the wildcard policy admin tool seems to time out when used on multiple
>>>>>> collections, or even large c

Re: [dspace-tech] Restrict access to logged-in users only

[José Geraldo]

Another option would be to backup your database and make changes to the
database.

Em qua., 3 de fev. de 2021 às 04:13, Sean Carte 
escreveu:

> For most collections, using the wildcard policy admin tool has worked very
> well, and I have been able to restrict their bitstreams to logged-in users.
> However, I have two collections with over 1000 items. For one of these,
> with 1688 items, I was not able to remove the anonymous read access; the
> browser reports an internal error, but there's nothing in the tomcat or
> dspace logs. Another collection, of 1012 items, allowed me to remove
> anonymous read access, but I have not been able to add READ access for the
> logged-in group.
>
> Apart from moving hundreds of items out of those collections, to reduce
> their size, does anybody have any suggestions on how I should proceed?
>
> DSpace version:  6.3
> XMLUI
> Mirage2 theme
>
> On Fri, 29 Jan 2021 at 20:48, Sean Carte  wrote:
>
>> Thanks again, José; you've been extremely helpful.
>>
>> On Fri, 29 Jan 2021 at 15:43, José Geraldo  wrote:
>>
>>> Hi,
>>>
>>> Items accepted in a collection inherit the associated authorization
>>> policies DEFAULT_ITEM_READ and DEFAULT_BITSTREAM_READ, which become READ
>>> policies for the item and its attachments.
>>>
>>> However, when changing the default policies for a collection, once items
>>> are accepted, the policies for existing items will not be changed
>>> automatically.
>>>
>>> Soon, a user, without logging in and in possession of the link to one of
>>> the items in the collection, will have access to the item and its contents.
>>>
>>> To get around this point, you will need to change the permissions of the
>>> items in the collection using the Policy Administration Tool to make them
>>> accessible only to logged-in users.
>>>
>>> For each item in a collection, there is only one READ policy configured
>>> for the Anonymous group.
>>>
>>> However, the tool does not have the option to edit policies, having only
>>> the options to add and delete policies.
>>>
>>> Therefore, it will be necessary to first delete the policies for items
>>> and binary files (attachments) and then create new READ policies linked to
>>> the special group for them.
>>>
>>> This process is done one collection at a time, if you need to apply to
>>> all collections, a suggestion would be to apply it to the database.
>>>
>>> Em sex., 29 de jan. de 2021 às 04:09, Sean Carte 
>>> escreveu:
>>>
>>>> Using the login.specialgroup, along with removing default read access
>>>> to the collections, does restrict access to collections listed on the home
>>>> page. However, anonymous access is still available to items made available
>>>> by Discovery. That is, in the 'Recently Added' section, or via search, or
>>>> the browse lists.
>>>>
>>>> Removing anonymous read access from items' bitstreams and replacing it
>>>> with read access for the authenticated special group does work, but I'm
>>>> going to have to repeat this process every time a new item is added. Also,
>>>> the wildcard policy admin tool seems to time out when used on multiple
>>>> collections, or even large collections (> ~1000), in which case the items
>>>> are not modified.
>>>>
>>>> I suppose I could modify the UI to remove the ability to use discovery,
>>>> etc., but that rather defeats the purpose of using DSpace.
>>>>
>>>> Is there a better approach?
>>>>
>>>> My goal is to have all items available to logged-in users, but nothing
>>>> available to anonymous users.
>>>>
>>>> DSpace version:  6.3
>>>> XMLUI
>>>> Mirage2 theme
>>>>
>>>> On Wed, 27 Jan 2021 at 15:28, Sean Carte  wrote:
>>>>
>>>>> Thanks, José!
>>>>>
>>>>> On Wed, 27 Jan 2021 at 14:54, José Geraldo  wrote:
>>>>>
>>>>>> Hi,
>>>>>>
>>>>>> You can use the "login.specialgroup" and change the READ policy for
>>>>>> this group.
>>>>>>
>>>>>>
>>>>>> https://wiki.lyrasis.org/display/DSDOC5x/Authentication+Plugins#AuthenticationPlugins-ConfiguringAuthenticationbyPassword
>>>>>>
>>>>>> Em qua., 27 de jan. de 2021 às 05:30, Sean Carte <
>>>>>

bug#44824: 27.1; Org export as pdf and open file does not open it

[Geraldo Biotti]

Il sab 30 gen 2021, 07:09 Lars Ingebrigtsen  ha scritto:

> Geraldo Biotti  writes:
>
> > I get the same results reported in bug 25234. 'M-! xdg-open
> /tmp/test.pdf' works
> > fine. I apologise for my english but it's not my mother language.
>
> So:
>
> This works:
> M-! xdg-open /tmp/test.pdf RET
>
> This doesn't work:
> M-& xdg-open /tmp/test.pdf RET
>
> This doesn't work:
> M-x shell RET xdg-open /tmp/test.pdf RET
>
> ?
>
> --
> (domestic pets only, the antidote for overdose, milk.)
>bloggy blog: http://lars.ingebrigtsen.no


Exactly. And it doesn't even "export as PDF and open file" in org-mode,
which I think is a related problem.