tags: bug, Debian

Action executed in 0.000

Each Tag

bug, Debian

Common tags - number of posts

Linux (6), Amarok (4), PowerMac G5 (3), TrickleUp (3), bridge (3), KDE (3), network (3), tracking (2), Ubuntu (2), report (2), SATA (2), music (2), Nagios (2), install (2), kernel (2), DOM (1), LTS (1), kernel module (1), MySQL (1), tunnel (1), visualization (1), paste (1), bonding (1), Katie (1), support (1), WoW (1), mapper (1), sysadmin (1), social media (1), font (1), randr (1), sushi (1), conference (1), how to (1), style (1), features (1), Sincora (1), Identica (1), funding (1), Raku (1), math (1), developer (1), software (1), Mitretek (1), packages (1), directory (1), Rubilicious (1), administrator (1), Konsole (1), gym (1), fosm (1), gsfonts (1), connection (1), blog (1), Graphviz (1), IRC (1), VPN (1), OSM (1), handbook (1), politics (1), operating system (1), OpenMoko (1), Bethesda (1), X11 (1), Pabs (1), geo (1), Gila (1), bookmarks (1), Java (1), badge (1), system administration (1), Mark (1), copy (1), database (1), crash (1), wiki (1), comments (1), ODP (1), address (1), Firefox (1), fontconfig (1), module (1), USPS (1), help (1), persistent (1),

3 way join

Amarok, Debian, bug

Sub groups 1

Debian, bridge, network (2), MySQL, bug, crash (1), Debian, Linux, system administration (1), Debian, Java, WoW (1), Debian, wiki (1), Debian, IRC, Katie, Pabs, Rubilicious, bookmarks (1), Debian, Graphviz, font, fontconfig, gsfonts (1), Debian, Linux, OSM, blog, fosm, geo, mapper, math, politics (1), Debian, Linux, operating system (1), Debian, VPN, bonding, bridge, connection, network, persistent, tunnel (1), Debian, PowerMac G5, SATA, install, kernel module (1), Debian, Ubuntu, developer (1), Debian, Ubuntu, packages, visualization (1), Debian, sysadmin (1), TrickleUp, bug, comments, database, kernel (1), Debian, Linux, help (1), Debian, Linux, conference (1), Debian, administrator, handbook (1), Debian, LTS, funding, support (1), Debian, OpenMoko (1), Bethesda, Debian, Linux, Mark, PowerMac G5, Raku, SATA, install, kernel, module, sushi (1), DOM, Firefox, bug (1), Debian, Identica, social media (1), Debian, X11, how to, randr (1), Debian, Gila, PowerMac G5, Sincora, TrickleUp, style (1), KDE, Konsole, bug, copy, paste (1), Mitretek, USPS, address, badge, bug, gym (1), Debian, ODP, directory, software (1), TrickleUp, bug, features (1)

Thank you Modestas and Mark, you brought the music back

tags: Amarok, music, KDE, Debian, bug
Amarok logo It's been a while, but after this bug was fixed and after Mark posted this, i finally have Amarok 2 playing music.

#501495 crash on powerpc: libamarok_collection-sqlcollection because of R_PPC_REL24 relocations

tags: Debian, bug, Amarok
Amarok 1.92.2-1 from experimental crashes, after an error dialog boxes shows up, with approximately the following text: ----------- Klib could not load module: libamarok_collection-sqlcollection

url: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=501495

type: project, format: page

There is, if only informally

tags: Debian, bug
You can submit your bugs to the Debian maintainers, and they'll handle it appropriately - see bugs.debian.org
parent post: On providing software feedback
notify me: yes

On providing software feedback

I've been using Nagios at work to monitor services across the network. Yesterday's upgrade failed. After fixing that i had some wishes for Nagios that i wanted to pass on. So my question for everyone is do i as (let's pretend i'm) a beginner speak to Debian where i got the software, or directly to Nagios?

On a philosophical note, i've thought about this a bit. I get my software directly from Debian. And Debian gets it from upstream, say Mozilla. Now as an experienced Debian user, i know which bugs are application bug and which ones are packaging bugs. But does the beginner or novice know this? Should they know this? I don't think so. Keeping it simple for the software user would be having a central location where they can provide feedback on software. And it makes sense that this is the place where the they got the software.

Unfortunately this line of thinking implies more work for packagers, namely reading more submissions, evaluating them, and passing some or most of them upstream. In this light, Debian becomes a virtual user of the upstream software. Debian forwards bugs on behalf of the user to upstream.

I'm curious to know if this sort of forwarding communication is built into the Debian structure. I guess not since software providers have various bug reporting interfaces. It would be cool if there Debian could forward bugs to any Bugzilla repository.