Krautspace/Unkraut
10
2
Issues 34 Projects 6 Activity

Drucken im Space #11

New issue
Open
opened 2023-10-11 21:49:49 +00:00 by l.behm · 2 comments
l.behm commented 2023-10-11 21:49:49 +00:00
Owner
Copy link

Ticket von @qbi vom 20.04.2023

berhsi kannst du mal im Wiki eine öffentliche Beschreibung hinterlassen, wie man den Drucker im Space benutzt? Am besten so als Schritt-für-Schritt-Anleitung, dass auch Fremde den einfach benutzen können.

> Ticket von @qbi vom 20.04.2023 > > berhsi kannst du mal im Wiki eine öffentliche Beschreibung hinterlassen, wie man den Drucker im Space benutzt? Am besten so als Schritt-für-Schritt-Anleitung, dass auch Fremde den einfach benutzen können.
bernd was assigned by l.behm 2023-10-11 21:49:49 +00:00
l.behm added this to the IT-Infrastruktur project 2023-10-11 21:49:49 +00:00
qbi added the
Kind/Enhancement
Kind/Documentation
Priority
Medium
 labels 2024-11-02 10:13:39 +00:00
qbi commented 2024-11-02 10:14:07 +00:00
Owner
Copy link

@bernd Ping. Wenn du magst, können wir das auch gemeinsam machen.

@bernd Ping. Wenn du magst, können wir das auch gemeinsam machen.
l.behm commented 2025-02-15 19:06:29 +00:00
Author
Owner
Copy link

Neulich hab ich in 2 frisch installierten Notebooks (Ubuntu 24LTS, Fedora 41) festgestellt, dass aus beiden WLANs (Krauttopf und freifunk) die Autodetection des Brother-Druckers funktioniert.
Generell ist aber von der Verwendung von cups-browserd abzuraten.

Neulich hab ich in 2 frisch installierten Notebooks (Ubuntu 24LTS, Fedora 41) festgestellt, dass aus beiden WLANs (Krauttopf und freifunk) die Autodetection des Brother-Druckers funktioniert. Generell ist aber von der Verwendung von [`cups-browserd`](https://www.cert.europa.eu/publications/security-advisories/2024-103/) abzuraten.
Sign in to join this conversation.
No Branch/Tag specified
Branches Tags
No results found.
No results found.
Labels
Clear labels   
Kind/Breaking

Breaking change that won't be backward compatible

  
Kind/Bug

Something is not working

  
Kind/Documentation

Documentation changes

  
Kind/Enhancement

Improve existing functionality

  
Kind/Feature

New functionality

  
Kind/Security

This is security issue

  
Kind/Testing

Issue or pull request related to testing

  
Priority
Critical
The priority is critical

  
Priority
High
The priority is high

  
Priority
Low
The priority is low

  
Priority
Medium
The priority is medium

  
Reviewed
Confirmed
Issue has been confirmed

  
Reviewed
Duplicate
This issue or pull request already exists

  
Reviewed
Invalid
Invalid issue

  
Reviewed
Won't Fix
This issue won't be fixed

  
Status
Abandoned
Somebody has started to work on this but abandoned work

  
Status
Blocked
Something is blocking this issue or pull request

  
Status
Need More Info
Feedback is required to reproduce issue or to continue work

  
bug

Something is not working

  
duplicate

This issue or pull request already exists

  
enhancement

New feature

  
help wanted

Need some help

  
invalid

Something is wrong

  
question

More information is needed

  
wontfix

This won't be fixed

No labels
Kind/Breaking
Kind/Bug
Kind/Documentation
Kind/Enhancement
Kind/Feature
Kind/Security
Kind/Testing
Priority
Critical
Priority
High
Priority
Low
Priority
Medium
Reviewed
Confirmed
Reviewed
Duplicate
Reviewed
Invalid
Reviewed
Won't Fix
Status
Abandoned
Status
Blocked
Status
Need More Info
bug
duplicate
enhancement
help wanted
invalid
question
wontfix
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
IT-Infrastruktur
Assignees
Clear assignees
No assignees
bernd
2 participants
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference: Krautspace/Unkraut#11
No description provided.
Delete branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?